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
Summary:
Currently, within a standalone argo-rollouts experiment, one has to write out the entire pod template for running experiments. It would be nice to reference existing/externally existing pod templates/deployments instead to allow for flexibility when using the experiments API.
Motivation:
I would like to use the experiments spec, and not the rollouts spec for testing deployments in my ArgoCD environments, but do not want to manage the pod specs in multiple places.
Points of Interest:
Some initial concerns/thoughts with this after chatting with @jessesuen
What will happen when the referenced spec is deleted or modified
What restrictions need to be made
What options are required when selecting/referencing a template to ensure uniqueness
Summary:
Currently, within a standalone argo-rollouts experiment, one has to write out the entire pod template for running experiments. It would be nice to reference existing/externally existing pod templates/deployments instead to allow for flexibility when using the experiments API.
Sample Potential Spec (from: @jessesuen )
Motivation:
I would like to use the experiments spec, and not the rollouts spec for testing deployments in my ArgoCD environments, but do not want to manage the pod specs in multiple places.
Points of Interest:
Some initial concerns/thoughts with this after chatting with @jessesuen
(Original Conversation on slack)
The text was updated successfully, but these errors were encountered: