Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE] Add support for argo rollouts as dependent workloads #57

Closed
aattuluri opened this issue Jan 17, 2020 · 0 comments
Closed

[FEATURE] Add support for argo rollouts as dependent workloads #57

aattuluri opened this issue Jan 17, 2020 · 0 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@aattuluri
Copy link
Contributor

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

@aattuluri aattuluri added the enhancement New feature or request label Jan 17, 2020
@aattuluri aattuluri added this to the v0.1 milestone Jan 21, 2020
@aattuluri aattuluri modified the milestones: v0.9, v1.0 Apr 6, 2020
itsLucario pushed a commit to itsLucario/admiral that referenced this issue Aug 9, 2022
…ate_docker_image

MESH-914: replaced all old docker image to new link
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants