Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove bastion related IAM resources #4

Closed
ialidzhikov opened this issue Nov 22, 2019 · 7 comments · Fixed by #139
Closed

Remove bastion related IAM resources #4

ialidzhikov opened this issue Nov 22, 2019 · 7 comments · Fixed by #139
Assignees
@DockToFuture @mvladev

Comments

@ialidzhikov
Copy link
Member

Currently we create the following bastion related IAM resources:

https://github.com/gardener/gardener-extensions/blob/1.0.0/controllers/provider-aws/charts/internal/aws-infra/templates/main.tf#L223-L268

We could remove them and move their creation to g/gardenctl.
@rfranzke
Copy link
Member

@DockToFuture can you take over and move the creation to gardenctl?

@rfranzke rfranzke transferred this issue from gardener-attic/gardener-extensions Jan 30, 2020
@rfranzke
Copy link
Member

rfranzke commented Mar 6, 2020

@DockToFuture any update?

@ghost ghost added the lifecycle/stale Nobody worked on this for 6 months (will further age) label May 6, 2020
@rfranzke
Copy link
Member

/ping @DockToFuture
/touch

@ghost
Copy link

ghost commented May 26, 2020

@DockToFuture

Message

/ping @DockToFuture
/touch

@ghost
Copy link

ghost commented May 26, 2020

@rfranzke Label "touch" does not exist for this repository.

@rfranzke rfranzke removed the lifecycle/stale Nobody worked on this for 6 months (will further age) label May 26, 2020
@vlerenc
Copy link
Member

vlerenc commented May 26, 2020

@rfranzke Not yet... hold your horses. That was just a dev version. ;-)

@mvladev mvladev mentioned this issue Jul 9, 2020
Merged
@mvladev
Copy link

mvladev commented Jul 9, 2020

I've opened a PR to remove the need for instance profiles when creating AWS bastion nodes in gardener-attic/gardenctl#218

I'll open a PR to remove those IAM resources from the infra

@mvladev mvladev self-assigned this Jul 9, 2020
@mvladev mvladev mentioned this issue Jul 9, 2020
Merged
@mvladev mvladev mentioned this issue Jul 20, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DockToFuture DockToFuture

@mvladev mvladev

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove bastion IAM role, profiles and policies mvladev/gardener-extension-provider-aws
5 participants
@vlerenc @ialidzhikov @rfranzke @DockToFuture @mvladev