Pause between pod identity installation and creation of the AzureIdentity #12
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
… the creation of any requested identities
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.
Background:
During a fresh install of pod identity if an AzureIdentity is created via helm immediately after installation of the pod identity chart sometimes the creation of the identity fails complaining that K8s doesn't know about the type "aadpodidentity.k8s.io/v1 AzureIdentity". This is because the CRDs from pod identity are not immediately applied, even though helm reports that pod identity has been successfully installed.
Fix:
Wait 30 seconds to add the AzureIdentity after pod identity has been installed. We only need to wait if CRDs are installed and the caller is requesting to add individual identities.