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

Rolling apply new resource group definition #274

Open
guilhem opened this issue Feb 5, 2025 · 2 comments
Open

Rolling apply new resource group definition #274

guilhem opened this issue Feb 5, 2025 · 2 comments

Comments

@guilhem
Copy link

guilhem commented Feb 5, 2025

Feature Description

Problem Statement:

When applying a new version of a resources group (for update, new feature etc), I want to control how it will be applied.

Proposed Solution:

having an update strategy field in spec.
controller following it for all instances of a crd.

Alternatives Considered:

N/A

Additional Context:

This kind of subject is already really hard to deal with in current controller model.
If it's solved with kro, it would be a game changer for many controllers.

  • Please vote on this issue by adding a 👍 reaction to the original issue
  • If you are interested in working on this feature, please leave a comment
@guilhem guilhem changed the title Rolling apply new group definition Rolling apply new resource group definition Feb 5, 2025
@barney-s
Copy link
Member

barney-s commented Feb 5, 2025

We were considering this part of earlier incarnation of KRO in the google repos. Lots of options here:

  • having a separate RGD for each breaking version. So that the teams can pick which one to roll out when
  • follow deployment controller pattern. auto-create a per-version RGD clone that is then rolled out according to a policy.
  • Rely on existsing tools like argocd to rollout change per namespace ..

Would like to understand the use-case as well as thoughts on building this in KRO vs using external tools to solve the problem.

@barney-s
Copy link
Member

barney-s commented Feb 5, 2025

related #206

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants