Allow ceph-client to be related with a warning to no longer manage #353
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kwmonroe
approved these changes
Jun 21, 2024
kwmonroe
pushed a commit
that referenced
this pull request
Jun 21, 2024
kwmonroe
pushed a commit
that referenced
this pull request
Jun 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Allow upgrading from 1.28 charms and prior while related over the
ceph-clientrelation. Will warn that ceph-client is a deprecated relationDetails
The kubernetes-control-plane charm should no longer manage ceph workloads, (ceph xfs, ceph rdb, ceph-fs) which instead should be delegated to the ceph-csi charm. For those upgrading from 1.28 when this relation existed, the existing workloads they are running deployed via the older versions of the charm will remain and be unmanaged by the charm. Post upgrade, one can remove the relation and the charm will not disturb its deployment.
LP: https://bugs.launchpad.net/charm-kubernetes-master/+bug/2070053