-
Notifications
You must be signed in to change notification settings - Fork 31
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
Deprecate Cluster resource migration guide #771
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for redpanda-docs-preview ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
||
| Operator v2.2.3-24.2.X | ||
| Migration path from the deprecated Cluster and Console custom resources. | ||
| As part of our ongoing enhancements, the deprecated Cluster and Console custom resources will not be migrated to the new Flux-based version. In the future, these custom resources will leverage the same reconciler that is currently used by Redpanda, ensuring a consistent and unified experience across all resources. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we should document the intent to unify the Cluster resource. That initiative is aimed at helping cloud and we don't want to encourage self hosted users to start using the Cluster CRD.
...We don't document anything about the Cluster or Console CRD for end users aside from this migration, right?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, Chris. Updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Description
Part of redpanda-data/redpanda-operator#237
Page previews
Checks