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

Support hash mode/custom channel in CSPO #99

Closed
michal-gubricky opened this issue Feb 19, 2024 · 0 comments · Fixed by #108
Closed

Support hash mode/custom channel in CSPO #99

michal-gubricky opened this issue Feb 19, 2024 · 0 comments · Fixed by #108
Assignees
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling Sprint Wellington Sprint Wellington (2024, cwk 08+09)

Comments

@michal-gubricky
Copy link
Contributor

michal-gubricky commented Feb 19, 2024

/kind feature

Describe the solution you'd like
Support the hash mode included as a feature of csmctl (refer to e.g., SovereignCloudStack/csctl#3). Currently, we only support the stable channel but we must include the option for multiple channels that follow a different versioning pattern.

This channel functionality can create a custom channel with versions such as v1-custom.xyz. This will allow using the hash mode of csmctl together with the Cluster Stack Provider OpenStack. See SovereignCloudStack/cluster-stack-operator#53.

@matofeder matofeder self-assigned this Feb 20, 2024
@jschoone jschoone added the Container Issues or pull requests relevant for Team 2: Container Infra and Tooling label Feb 28, 2024
@jschoone jschoone added the Sprint Wellington Sprint Wellington (2024, cwk 08+09) label Feb 28, 2024
@jschoone jschoone moved this from Backlog to Done in Sovereign Cloud Stack Feb 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Container Issues or pull requests relevant for Team 2: Container Infra and Tooling Sprint Wellington Sprint Wellington (2024, cwk 08+09)
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants