Argo Rollouts should be an option in the argocd dashboard, instead of having two dashboards and lack of logging in argocd makes it hard to troubleshoot sometimes with analysis templates.
You can and should use ArgoCD and Rollouts in all environments. ArgoCD is for installing/syncing your applications and Rollouts is for rolling out updates to the container image
Hi sir thanks for the video I have one doubt using localhost you’re accessing rollout dashboard using port forwarding instead of that how to create ingress for rollout dashboard service that will always up and running for app team usages so that they can easily promote the deployment
@@palanisamy-dl9qe Install with a helmchart and set dashboard enabled to true github.com/devopsjourney1/homelab-services/blob/868526431cacfb5d25b6f97eeb2c9575a9f6035a/k8s/argo-rollouts/values.yaml#L6
@@DevOpsJourney thanks for sharing if I enable dashboard server true by default rollout dashboard will be installed in my eks cluster? This will create default endpoint url to access the rollout UI page is that correct understanding?
This is really great and awesome! Thank you so much for keeping us updated.
Thank you so much brother , really high quality content ❤💯
Great timing! I'm leaning DevOps at this part! Thank you!
Argo Rollouts should be an option in the argocd dashboard, instead of having two dashboards and lack of logging in argocd makes it hard to troubleshoot sometimes with analysis templates.
Now i got rollouts concept completely. Thanks🙏
Great video. Do more content with Argo CD, it's absolutely a game-changer tool.
Nice video, there is flagger too for the same job. You can try both before you use it In production
Such an amazing tutorial. I appreciate it a lot!
Awesome high quality content, thank you.
Thanks for the video. By the way nice theme for your terminal. Which theme is it?
Great video do you plan to cover Argo events as well
Thanks for your video!
Would you say argo rollout is used for production deployment and argocd is used for qa env? or can you use argo rollout for both qa and prod?
You can and should use ArgoCD and Rollouts in all environments. ArgoCD is for installing/syncing your applications and Rollouts is for rolling out updates to the container image
Hi sir thanks for the video I have one doubt using localhost you’re accessing rollout dashboard using port forwarding instead of that how to create ingress for rollout dashboard service that will always up and running for app team usages so that they can easily promote the deployment
Yes that's the way I'd do it for most environments, good call.
@@DevOpsJourney can you please give me the document if you have anything in your blog! Because I want configure in my eks cluster
@@palanisamy-dl9qe Install with a helmchart and set dashboard enabled to true github.com/devopsjourney1/homelab-services/blob/868526431cacfb5d25b6f97eeb2c9575a9f6035a/k8s/argo-rollouts/values.yaml#L6
@@DevOpsJourney thanks for sharing if I enable dashboard server true by default rollout dashboard will be installed in my eks cluster?
This will create default endpoint url to access the rollout UI page is that correct understanding?
@@palanisamy-dl9qe yup!
so basically canary deployement with ARGO
Yup 👍