Argo Rollouts extensions #2133
spaghettifunk
started this conversation in
Ideas
Replies: 1 comment 2 replies
-
|
@spaghettifunk Argo Rollouts has just released plugins in 1.5 https://argoproj.github.io/argo-rollouts/plugins/ (both for traffic providers and analysis providers)
There is already a plugin for the Kubernetes Gateway API https://github.com/argoproj-labs/rollouts-plugin-trafficrouter-gatewayapi |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hey folks 👋 I love Argo Rollouts and I cannot thank you enough for this amazing project!
I have been working with Knative Serving for a while and I've been trying to figure out how I could combine Argo Rollouts and Knative together so that I could take advantage of all the goodies that Argo Rollouts has to offer and, at the same time, the simplicity of deploying applications with Knative Serving. I am aware of the discussion that happened here and I totally understand the issue and the developer experience that is at the base.
This made me thinking: what if Argo Rollouts would have
extensionslike Argo CD? Would it be possible for Argo Rollout to control CRDs as well? How can Argo Rollouts "control" a generic CRD without knowing in advance what it is?Where I am trying to get is basically the possibility to make available a set of
interfacesthat could be implemented by the external party that has the knowledge of the CRD. From Argo Rollouts perspective, theRolloutspecification will have a reference to the code where theinterfacesare implemented (like in ArgoCD) and theworkloadRefwould point to the CRD specification.The
Controllerwould now call theinterfacesto execute the Rollout strategy.AnalysisandExperimentsshouldn't be touched by the external party since they are independent from the strategy itself.Does it make sense? 🙈
Beta Was this translation helpful? Give feedback.
All reactions