Nice hands on practical approach. Like it! I hope there will be more videos and tutorials on argo cd in general. Life is too short to be imperative and manual ;)
Amazing! In this case, you can really use any prometheus installation -- I am using the stack to build in future tutorials on this work, using Grafana etc. :)
Thanks alot for this effective explanation. I have just a question : how can we depoy the same app into multiple namespaces? For example : app1 is deployed to dev namespaces with argocd, so when i try to deploy same app to test namespace ( with same app name ofcurse) argocd does not allow deploying with same names (even in different projects)
So you are saying, you have app1 that you would like to run in namespace A and in namespace B? It would be bad practice to duplicate the app through ArgoCD. Instead, you want to increase the replicaset e.g. to 4 and select the node affinity so the replicas are scheduled to different nodes (that is something you would want in case a node dies) however, the namespaces are there to divide users, types of deployments etc. kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
@@AnaisUrlichs thanks for your reply, In many situations I have to deploy same app on multiple stages,so for every stage I have a namespace.. but argocd doesn't let you ( by default) deploy argocdApp in different namespace . So it let you deploy apps in "argocd namespace" where argocd instance lives.
Thanks for the depth in this tutorial! I love it!
Nice hands on practical approach. Like it! I hope there will be more videos and tutorials on argo cd in general. Life is too short to be imperative and manual ;)
Thanks. You deploy with kubectl but the apps are visible in argocd. Is that because they are deployed in the argocd namespace?
Great tutorial, very well explained.
I have implemented the same tools for a final master project but using kube prometheus.
Amazing! In this case, you can really use any prometheus installation -- I am using the stack to build in future tutorials on this work, using Grafana etc. :)
Really awsome
Awesome video as usual 😊
top tutorial Anais !
Thank you ☺
Really Awesome.
Thanks alot for this effective explanation.
I have just a question : how can we depoy the same app into multiple namespaces? For example : app1 is deployed to dev namespaces with argocd, so when i try to deploy same app to test namespace ( with same app name ofcurse) argocd does not allow deploying with same names (even in different projects)
So you are saying, you have app1 that you would like to run in namespace A and in namespace B? It would be bad practice to duplicate the app through ArgoCD. Instead, you want to increase the replicaset e.g. to 4 and select the node affinity so the replicas are scheduled to different nodes (that is something you would want in case a node dies) however, the namespaces are there to divide users, types of deployments etc. kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
@@AnaisUrlichs thanks for your reply,
In many situations I have to deploy same app on multiple stages,so for every stage I have a namespace.. but argocd doesn't let you ( by default) deploy argocdApp in different namespace . So it let you deploy apps in "argocd namespace" where argocd instance lives.