K8SPSMDB-1156: simplify smartUpdate if rs isn't initialized #1708
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.
https://perconadev.atlassian.net/browse/K8SPSMDB-1156
DESCRIPTION
Problem:
When the cluster is deployed with
spec.tls.allowInvalidCertificates: false
, it enters an error state, making it impossible to update this setting tospec.tls.allowInvalidCertificates: true
Cause:
After setting
spec.tls.allowInvalidCertificates: true
, the operator attempts to connect to the pods of replica set, which has not been initialized.Solution:
The operator should avoid connecting to pods during smart update if the replica set has not been initialized.
CHECKLIST
Jira
Needs Doc
) and QA (Needs QA
)?Tests
compare/*-oc.yml
)?Config/Logging/Testability