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.

Sign up for GitHub

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

Jump to bottom

[Story] Remove ClusterCryostat CRD #732

Closed
Tracked by #731
ebaron opened this issue Feb 13, 2024 · 0 comments · Fixed by #737
Closed
Tracked by #731

[Story] Remove ClusterCryostat CRD #732

ebaron opened this issue Feb 13, 2024 · 0 comments · Fixed by #737
Assignees
@ebaron
Labels
breaking change This change (potentially) breaks API compatibility and requires corresponding changes elsewhere chore Refactor, rename, cleanup, etc.

Comments

@ebaron
Copy link
Member

ebaron commented Feb 13, 2024

After #583, ClusterCryostat no longer provides any value beyond what the Cryostat CRD can do. Since we're updating to a new major version, we should get rid of it in order to simplify things.
@ebaron ebaron added chore Refactor, rename, cleanup, etc. breaking change This change (potentially) breaks API compatibility and requires corresponding changes elsewhere labels Feb 13, 2024
@ebaron ebaron self-assigned this Feb 13, 2024
This was referenced Feb 13, 2024
Closed
Merged
@ebaron ebaron linked a pull request Feb 16, 2024 that will close this issue
chore(api): remove ClusterCryostat CRD #737
Merged
7 tasks
@ebaron ebaron closed this as completed Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ebaron ebaron

Labels
breaking change This change (potentially) breaks API compatibility and requires corresponding changes elsewhere chore Refactor, rename, cleanup, etc.
Projects
No open projects
3.0.0 release
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore(api): remove ClusterCryostat CRD ebaron/cryostat-operator
1 participant
@ebaron