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.

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

Allow using IAM Profiles for etcd S3 credentials #512

Open
ethanchowell opened this issue Dec 6, 2024 · 0 comments
Open

Allow using IAM Profiles for etcd S3 credentials #512

ethanchowell opened this issue Dec 6, 2024 · 0 comments
Assignees
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@ethanchowell
Copy link

Describe the solution you'd like:
[A clear and concise description of what you want to happen.]
It would be great to remove the requirement for etcd s3 credentials for the scenario of users restricted to temporary credentials or usage of IAM profiles.

Why do you want this feature:
Currently if you don't provide credentials to the server config for S3 backups the controller will fail. For users that can only use temporary credentials this is problematic. A warning log saying something like "no credentials provided, relying on IAM" or even a flag to explicitly ignore providing credentials would be

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@ethanchowell ethanchowell added kind/feature New feature or request needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 6, 2024
@ethanchowell ethanchowell changed the title ALlow using IAM Profiles for etcd S3 credentials Allow using IAM Profiles for etcd S3 credentials Dec 6, 2024
@alexander-demicev alexander-demicev added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-priority Indicates an issue or PR needs a priority assigning to it needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 3, 2025
@kkaempf kkaempf added this to the v0.11.0 milestone Jan 3, 2025
@salasberryfin salasberryfin self-assigned this Jan 8, 2025
@salasberryfin salasberryfin moved this from CAPI Backlog to In Progress (8 max) in CAPI & Hosted Kubernetes providers (EKS/AKS/GKE) Jan 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

No branches or pull requests

4 participants