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

Rollout for group of Deployment #4054

Open
matiasah opened this issue Jan 16, 2025 · 0 comments
Open

Rollout for group of Deployment #4054

matiasah opened this issue Jan 16, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@matiasah
Copy link

matiasah commented Jan 16, 2025

Summary

It would be useful if Argo Rollouts was able to handle a group of Deployment objects, or have a separate custom resource to handle different variations of a Deployment.
Currently the Rollout resource only handles ReplicaSets that matches only one Deployment object, but different implementations could vary in nodeSelector / nodeAffinity.

Use Cases

In Google Kubernetes Engine, it's possible to save costs by using dual deployments of standard and spot virtual machines. Spot VMs are cheaper and can be used in greater numbers to increase compute capacity at low cost.

  • A Kubernetes Service is going to be pointing at all times to two different ReplicaSet resources (one spot, one standard).
  • The dual ReplicaSets resources are going to have the same images, volumes, labels, etc.
  • The dual ReplicaSets are going to differ in nodeAffinity / nodeSelector labels, as one is going to match specifically spot VMs while the other is going to use standard VMs.
@matiasah matiasah added the enhancement New feature or request label Jan 16, 2025
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

1 participant