Awsome video, clean and informative! A interesting follow up would be how to hook this up with the CI part. commit, build test to creating the artifact that is releasable here.
That was excellent, very clear and informative, I'm already looking forward to more videos. One question, I am curious what is a good folder structure for a production ArgoCD with several environments and apps.
So that really depends on your project. To me, it depends more on who your target audience is, and what their competency is regarding infrastructure. I tend to like to keep things in Helm if the people managing it are trained on Kubernetes. I keep these helm charts in the "infra" repo, and I usually have one helm chart, which acts as the master gitops chart which deploys all the rest. You can provide different values.yaml files for different environments, and I might make a follow-up video on how to do exactly that. Then in the application repo, which is usually co-maintained by the developers & infra, I usually like to use Kustomize or a simple helm chart, which little logic. I usually put this at the root of the target repos directory, usually in an /infra folder.
Awsome video, clean and informative! A interesting follow up would be how to hook this up with the CI part. commit, build test to creating the artifact that is releasable here.
Hey, I will see about making this the next video as there seems to be some interest. Thank you for the insights.
@@PolitePixels Awsome! Tekton looks nice :)
That was excellent, very clear and informative, I'm already looking forward to more videos. One question, I am curious what is a good folder structure for a production ArgoCD with several environments and apps.
So that really depends on your project. To me, it depends more on who your target audience is, and what their competency is regarding infrastructure.
I tend to like to keep things in Helm if the people managing it are trained on Kubernetes. I keep these helm charts in the "infra" repo, and I usually have one helm chart, which acts as the master gitops chart which deploys all the rest.
You can provide different values.yaml files for different environments, and I might make a follow-up video on how to do exactly that.
Then in the application repo, which is usually co-maintained by the developers & infra, I usually like to use Kustomize or a simple helm chart, which little logic.
I usually put this at the root of the target repos directory, usually in an /infra folder.
great content, where we can find the video with the pipeline integration? Thanks