cluster-api-provider-aws
cluster-api-provider-aws copied to clipboard
kubernetes-sigs
Role creation for use with EKS addons
/kind feature /area provider/eks /help
Describe the solution you'd like I would like a way for CAPA to create a role with the required permissions for use with EKS addons. Currently, you need to create the role outside of CAPA and supply the ARN when declaring the addon.
There would be significant UX benefits from this.
Relates to #2139
@richardcase: This request has been marked as needing help from a contributor.
Please ensure the request meets the requirements listed here.
If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.
In response to this:
/kind feature /area provider/eks /help
Describe the solution you'd like I would like a way for CAPA to create a role with the required permissions for use with EKS addons. Currently, you need to create the role outside of CAPA and supply the ARN when declaring the addon.
There would be significant UX benefits from this.
Relates to #2139
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
Sorry, I totally forgot I assigned this issue to myself... Let me work on it! 🙇
Sorry, I totally forgot I assigned this issue to myself... Let me work on it! 🙇
No problem at all. Feel free to ping me if you need anything.
@richardcase Sorry, I've started looking into the issue but found it was a little bit more complicated than I originally thought. I'm afraid I cannot provide the feature in a timely manner so would you or others take the issue instead...? 🙇
I'll unassign but if you change your mind or want help then feel free to ping me.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.
This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue or PR as fresh with
/remove-lifecycle stale - Mark this issue or PR as rotten with
/lifecycle rotten - Close this issue or PR with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
