Fix ServiceAccount readiness logic for k8s v1.24+ #2099
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Starting in Kubernetes v1.24, the default behavior for ServiceAccount resources changed so that a secret is no longer provisioned. This change updates our await logic to only wait for the secret to exist for ServiceAccount resources on older clusters, and immediately returns ready for newer clusters.
Does the PR have any schema changes?Looking good! No breaking changes found. |
viveklak
approved these changes
Jul 25, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Proposed changes
Starting in Kubernetes v1.24, the default behavior for ServiceAccount resources changed so that a secret is no longer provisioned. This change updates our await logic to only wait for the secret to exist for ServiceAccount resources on older clusters, and immediately returns ready for newer clusters.
Related issues (optional)
Fix #2063