You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We can easily install argo-rollouts via the stacks/package feature, but we don't have a good way to install the argo-rollouts extension that adds argo-rollouts features to the argocd UI.
Possible Solution
The easiest solution is to install the rollout extension in every cluster using the instructions in https://github.com/argoproj-labs/rollout-extension but I'm not sure if that's an acceptable solution.
Alternatives Considered
We don't have a great way to customize our argocd install at cluster creation time from what I'm seeing due to our kustomize build of the manifests at compile time. Not sure if we want a way to render templates for our argocd install at cluster creation time, it seems like a significant maintenance add but might be necessary for some features.
The text was updated successfully, but these errors were encountered:
Either from a Makefile or manually, where the yaml file is the patch listed from the docs; re-running idpbuilder create does not appear to undo this patch
Have you searched for this feature request?
Problem Statement
We can easily install argo-rollouts via the stacks/package feature, but we don't have a good way to install the argo-rollouts extension that adds argo-rollouts features to the argocd UI.
Possible Solution
The easiest solution is to install the rollout extension in every cluster using the instructions in https://github.com/argoproj-labs/rollout-extension but I'm not sure if that's an acceptable solution.
Alternatives Considered
We don't have a great way to customize our argocd install at cluster creation time from what I'm seeing due to our
kustomize build
of the manifests at compile time. Not sure if we want a way to render templates for our argocd install at cluster creation time, it seems like a significant maintenance add but might be necessary for some features.The text was updated successfully, but these errors were encountered: