return error when Kube API is down during statefulset sync #2064
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.
fixes #2031
I think the refactor in #1848 has introduced this regression, do you think it was intended?
Before the refactor,
getPodEnvironmentSecretVariables
andgetPodEnvironmentConfigMapVariables
were called directly ingenerateStatefulSet
and we used to return an error (and halt the sync) instead of just logging the error and continue sync with missing data.Maybe add a test and adjust documentation somewhere.