cluster-api-provider-aws
cluster-api-provider-aws copied to clipboard
DOCS: Updated AWS Management Cluster docs
/kind feature
https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/master/docs/book/src/topics/using-cluster-api-with-cross-account-role-assumption.md
These instructions still mention clusterctl alpha phases
which is no longer viable. These docs need to be updated.
/help /good-first-issue /kind documentation
@richardcase: This request has been marked as suitable for new contributors.
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-good-first-issue
command.
In response to this:
/help /good-first-issue /kind documentation
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.
I'm happy to contribute. /assign
I got sidetracked, don't want to hold this to be implemented, feel free to re-assign it.
@Evalle - we've added a milestone of 0.7.0 to this, so there is plenty of time if you would still like to do this?
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
/lifecycle frozen
@richardcase : I can work on it, but I would require a little help and insight on the task. Thank you
Thanks @sayantani11.
I think maybe there are 2 parts to this:
- Updating the above linked doc so that it doesn't reference
clusterctl alpha
and instead uses the correct clusterctl args - Splitting the docs into 2 sections: a. existing cross account role assumption using kiam b. new section on using AWSClusterRoleIdentity for the cross role assumption.
Feel free to ping me here or in #cluster-api-aws
Let's sort this out, and cross-reference with multi-tenancy /priority important-soon
TODO: Remove the KIAM documents and point to Multi-tenancy instead.
Could be done together with https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2105
/remove-lifecycle frozen
/milestone Backlog
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/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied,lifecycle/rotten
is applied - After 30d of inactivity since
lifecycle/rotten
was 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
@richardcase @cdenneen Is this issue still not resolved as I'd like to work on this if needed