allow juju add-unit to inherit IAM policies from AWS
Bug #1715200 reported by
Adam Stokes
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Low
|
Unassigned |
Bug Description
Currently, conjure-up can set IAM policies on everything it initially deploys. However, anyone wanting to do add-unit's will not inherit those policies and ultimately fail to do things such as join existing kubernetes cluster that have CNI enabled.
I'm not sure if this is something we could utilize in the model config and have juju check for IAM policies if provider == ec2 or what the best approach is.
Some reference https:/
tags: | added: conjure |
tags: | added: ec2-provider |
Changed in juju: | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in juju: | |
importance: | High → Medium |
To post a comment you must log in.
Specifically, we need something akin to the resource-tags model config but for IAM roles.