K8SPG-833: watch envFrom secrets
#1306
Merged
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/K8SPG-833
DESCRIPTION
This PR fixes two issues:
envFrombut does not exist, the operator proceeds to create the cluster and fails. With these changes the operator will not create or update a cluster until the secret exists.envFromsecret is updated. Currently, it only watches secrets with thepostgres-operator.crunchydata.com/clusterlabel. To call reconcile onenvFromsecrets update, the field index was added that allows to list all clusters referencing a specificenvFromsecret. Using this index, the newwatchEnvFromSecretsfunction will call reconcile for clusters that depend on those secretsThere are no unit tests for this change, because it is difficult to test watch functions. All related tests were previously removed for this reason
CHECKLIST
Jira
Needs Doc) and QA (Needs QA)?Tests
Config/Logging/Testability