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
Is your feature request related to a problem? Please describe.
Currently, admiral finds k8s deployments based on the dependency CR to create global CNAMEs in the dependent clusters. Argo rollouts is another way to deploy workloads and admiral doesn't support watching them as a dependent workload.
Describe the solution you'd like
An argo rollout CRD should be treated similar to k8s deployment when identifying the dependent workloads (based of the identifier mechanism used for deployments) when creating global CNAMEs for workloads
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently, admiral finds k8s deployments based on the dependency CR to create global CNAMEs in the dependent clusters. Argo rollouts is another way to deploy workloads and admiral doesn't support watching them as a dependent workload.
Describe the solution you'd like
An argo rollout CRD should be treated similar to k8s deployment when identifying the dependent workloads (based of the identifier mechanism used for deployments) when creating global CNAMEs for workloads
The text was updated successfully, but these errors were encountered: