Skip to content

Conversation

@fabiomatavelli
Copy link

Adds the aws-iam-authenticator to Talos.

@fabiomatavelli fabiomatavelli force-pushed the feat/add-aws-iam-authenticator branch 3 times, most recently from 454d2f5 to 265ebc6 Compare January 2, 2026 15:56
@fabiomatavelli fabiomatavelli changed the title (WIP) feat: add aws-iam-authenticator exntesion (WIP) feat: add aws-iam-authenticator extension Jan 2, 2026
@fabiomatavelli fabiomatavelli force-pushed the feat/add-aws-iam-authenticator branch 2 times, most recently from f6ae4f2 to 409c27c Compare January 2, 2026 16:30
Adds the [aws-iam-authenticator](kubernetes-sigs/aws-iam-authenticator) extension to Talos so it can generate the necessary certificates and kubeconfig, to be used with `kube-apiserver`, so users can authenticate in the cluster using AWS IAM roles.
@fabiomatavelli fabiomatavelli force-pushed the feat/add-aws-iam-authenticator branch from 409c27c to e8cebbe Compare January 2, 2026 16:39
@frezbo
Copy link
Member

frezbo commented Jan 13, 2026

@fabiomatavelli is this good for review?

@fabiomatavelli
Copy link
Author

@frezbo I'm still thinking if it would make sense to add this or not tbh. With the extension the process would be executed on all the nodes (worker and control-planes) as it requires the configuration to be present. So, I'm thinking if it makes sense to move forward with the extension or if providing the necessary files (certs and kubeconfig) during the bootstrap of the nodes would make more sense.

@frezbo
Copy link
Member

frezbo commented Jan 19, 2026

Cool, iterate and see how it goes, we've plenty of time before 1.13

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants