-
Notifications
You must be signed in to change notification settings - Fork 11
CLOUDP-331496: Remove undocumented operator.enablePVCResize
Helm value
#272
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
base: master
Are you sure you want to change the base?
Conversation
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.
Agree, let's remove the undocumented field.
@@ -4,7 +4,7 @@ | |||
# MCK 1.3.0 Release Notes | |||
|
|||
## Other Changes | |||
* Optional permissions for `PersistentVolumeClaim` moved to a separate role. When managing the operator with Helm it is possible to disable permissions for `PersistentVolumeClaim` resources by setting `operator.enablePVCResize` value to `false` (`true` by default). When enabled, previously these permissions were part of the primary operator role. With this change, permissions have a separate role. | |||
* The undocumented `operator.enablePVCResize` Helm value has been removed. If you previously set this value to `false`, please note that the operator roles will now include permissions for `PersistentVolumeClaim` resources by default. |
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.
This should be considered a breaking change, so requiring bumping major version...
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.
Arguably it is not a breaking change since we are adding new RBAC by default. Yes, we are removing the setting which only appears in values.yaml
, but at runtime it won't negatively affect the operator or workloads.
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.
Removing this switch should be considered as a breaking change.
Summary
In #260 I moved
PersistentVolumeClaim
permissions into a separate role, enabling modularity because these permissions are controlled byoperator.enablePVCResize
Helm value and appeared to be optional.Later I noticed that
operator.enablePVCResize
is undocumented.I propose that we revert changes done in #260 and remove the undocumented setting. Permissions are enabled by default already and I do not think there is a rationale for this to be configurable.
Furthermore - we do not test this with
operator.enablePVCResize
set tofalse
. We don't even know if the operator will still function correctly without the permissions.Proof of Work
N/A - CI must be green.
Checklist
Reminder (Please remove this when merging)