This repository has been archived by the owner on Jul 25, 2022. It is now read-only.
Remove AWS instance profile from bastion nodes #218
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
AWS IAM Instance Profiles are not needed for bastions as they should be used only to jump to the broken instances.
gardener-robot-ci-3
added
reviewed/ok-to-test
This was referenced Jul 9, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What this PR does / why we need it:
AWS IAM Instance Profiles are not needed for bastions as they should be used only to jump to the broken instances.
See AWS EC2 RunInstances API.
Which issue(s) this PR fixes:
Fixes # n/a
Special notes for your reviewer:
Related issue gardener/gardener-extension-provider-aws#4
Release note: