Update deploy.md to use IRSA instead of pod identities #645
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 method explained in pod identities section is error prone and doesn't create the required resources. Hence, going for IRSA is recommended.
|
Hi @gaurarpit12 , which step of the Pod Identities setup not work for you? could you help to share the error message? I tried on my side these steps work for me. |
|
@zijun726911 , The steps didn't create what is required, when using pod identities. However, IRSA works fine. Hence, IRSA should be the default one to be used |
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.
The method explained in pod identities section is error prone and doesn't create the required resources. Hence, going for IRSA is recommended.
What type of PR is this?
Which issue does this PR fix:
What does this PR do / Why do we need it: To ensure that users use the correct methodology
If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:
Testing done on this change:
Automation added to e2e:
Will this PR introduce any new dependencies?:
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.