tkestack / tkestack/tke-extend-network-controller
[Question] 有无支持角色的计划？
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 14
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
如题，目前需要创建一个子账号提供API密钥来操作负载均衡，能否通过SDK自带的凭证管理，实现动态获取角色的API密钥，这样子就不用将密钥存储在集群内了。
同时还能省去 管理子账号，密钥轮换 等一系列操作（一些情况下不能复用子账号，但可以复用角色）
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files or tests. First read the linked Go SDK credential-management documentation and inspect how load-balancer credentials are currently configured; clarify the role-credential flow and its cluster-storage constraints. Done means the project has an agreed implementation scope and acceptance criteria for dynamic role credentials.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cloud, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100