requeue spoke token controller until the application-manager SA secre… #410
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.
…t token is ready
https://issues.redhat.com/browse/ACM-13250
The fix is to address the issue found in AKS cluster
When the SA token secret
open-cluster-management-agent-addon/application-manager
was created, AKS didn't generate the token right away. So the spoken token controller regards it as an invalid token secret, and the secret was deleted and regenerated.We observed the token secret was in create-delete-recreate-delete loop for over 1 hour. Once AKS cluster performance is back, the SA token secret was created with the token as expected. Consequently the AKS cluster secret was generated in the ArgoCD NS