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

Allow user to specify curated packageBundle version during cluster install #8422

Open
anashakt opened this issue Jul 1, 2024 · 1 comment

Comments

@anashakt
Copy link

anashakt commented Jul 1, 2024

What would you like to be added:
Currently versioning of curated package bundle is not allowed because of by default latest curated package bundle gets activated on the cluster. I would like to have a key in the cluster spec using which one can specify a packagebundle version.

Why is this needed:
It allows controlled release of packages in production. If QA team has tested EKSA cluster lifecycle against a specific packageBundle version then production should get the same version as opposed to latest available at the time of cluster creation in Production.

@tatlat
Copy link
Member

tatlat commented Jul 5, 2024

Thanks for bringing this up! We will add it to the backlog for now and discuss priority internally.

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

No branches or pull requests

2 participants