Kostis (Codefresh)

This is a very interesting use case. But should it really be handled by Argo Rollouts? Maybe ArgoCD is better instead (e.g. as an extension of health checks)?

Hello. The reason that this question has been not answered, is that there is no standard answer. Most companies do something different and either have an ad-hoc solution or something...

@qxmips It is already on my TODO list. Stay tuned :-)

@qxmips , @emirot , @taybur43 Here is the example repo https://github.com/kostis-codefresh/gitops-environment-promotion Article with more details about the suggested structure https://codefresh.io/about-gitops/how-to-model-your-gitops-environments-and-promote-releases-between-them/ Article about what to avoid https://codefresh.io/about-gitops/branches-gitops-environments/ Any feedback welcome.

Hey @ReubenTheDS Thank you for the feedack. 1) Yes the same docker image should be promoted to all environments (but with different configuration). Actually this was a good practice already...

I am working on this

Hey @sbose78 I would be happy to help with this. I already have some ideas on how to improved the docs in Argo Rollouts. In summary, right now most of...

You can simply change the warning message to "To use the cluster subdomain feature you need to have an ingress controller in your cluster" The confusing part is that you...

Yes, apparently the chart was installed ok after all. There are too many entries in the Audit dashboard. I cannot seem to find the one responsible for this task.

With the new version I got ``` ./vcluster-linux-amd64 create sample1 -n virtual-kostis-codefresh [info] execute command: helm upgrade sample1 vcluster --repo https://charts.loft.sh --version 0.3.1-alpha.0 --kubeconfig /tmp/327907676 --namespace virtual-kostis-codefresh --install --repository-config='' --values...