-
Notifications
You must be signed in to change notification settings - Fork 179
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
Move resolution of developerMode and additionalScyllaDBArguments to Operator #2137
Move resolution of developerMode and additionalScyllaDBArguments to Operator #2137
Conversation
a4eae74
to
cf5b5bd
Compare
helm/scylla-operator/templates/scyllacluster_member_clusterrole_def.yaml
Outdated
Show resolved
Hide resolved
This should go in a dedicated PR, especially for visibility. |
cf5b5bd
to
352c0e4
Compare
352c0e4
to
f4f707b
Compare
f4f707b
to
2b93f00
Compare
2b93f00
to
3c1b469
Compare
extracted to separate PR #2139 |
/hold for prereq #2139 |
3c1b469
to
858d3ba
Compare
#2139 landed |
858d3ba
to
a31126b
Compare
a578a31
to
281d62b
Compare
@rzetelskik @tnozicka ptal |
9a9a07b
to
adb86f2
Compare
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
/assign tnozicka
adb86f2
to
85f60ec
Compare
…to Operator Moves the resolution of developerMode and additionalScyllaDBArguments from the sidecar to the Operator. This change addresses an issue where modifications to these arguments did not trigger a rolling restart of the ScyllaDB cluster. By moving the logic to the Operator, any changes to these fields now correctly trigger a rolling restart as intended. Since the sidecar no longer needs to fetch the ScyllaCluster resource for these parameters, it no longer requires permissions to perform GET operations on ScyllaCluster objects. However, to ensure a safe rolling upgrade of the Operator, these permissions are not removed yet.
85f60ec
to
b55a97a
Compare
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 for the updates
overall lgtm, but 2 nits would simplify branching and a testing matrix
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rzetelskik, tnozicka, zimnx The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
ScyllaDB contianer image enables developerMode if it's not explicitly disabled. It's the opposite logic to what we had in the past, which was changed in scylladb#2137 by mistake. This restores previous logic of explicitly disabling developerMode unless it's enabled in the API object.
ScyllaDB contianer image enables developerMode if it's not explicitly disabled. It's the opposite logic to what we had in the past, which was changed in scylladb#2137 by mistake. This restores previous logic of explicitly disabling developerMode unless it's enabled in the API object.
Moves the resolution of
developerMode
andadditionalScyllaDBArguments
from the sidecar to the Operator.This change addresses an issue where modifications to these arguments did not trigger a rolling restart of the ScyllaDB cluster.
By moving the logic to the Operator, any changes to these fields now correctly trigger a rolling restart as intended.
Since the sidecar no longer needs to fetch the ScyllaCluster resource for these parameters, it no longer requires permissions to perform GET operations on ScyllaCluster objects.
However, to ensure a safe rolling upgrade of the Operator, these permissions are not removed yet.
Additionally, this commit removes support for the deprecated
cpuset
field. It is now treated as if it is always set to true regardless of its value.Requires:
cpuset
field #2139Fixes #1389