-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Update AWS IAM Authenticator to 0.5.0 #8423
Update AWS IAM Authenticator to 0.5.0 #8423
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
upup/models/cloudup/resources/addons/authentication.aws/k8s-1.12.yaml.template
Outdated
Show resolved
Hide resolved
3a66eed
to
c0b4f62
Compare
upup/models/cloudup/resources/addons/authentication.aws/k8s-1.12.yaml.template
Outdated
Show resolved
Hide resolved
c0b4f62
to
ccabe51
Compare
/hold for discussion in kubernetes-sigs/aws-iam-authenticator#287 |
/test all |
I merged changes from these manifests: https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/v0.5.0/deploy/example.yaml https://github.com/kubernetes-sigs/aws-iam-authenticator/blob/v0.5.0/deploy/iamidentitymapping.yaml The new version supports replacing the configmap with a IAMIdentityMapping custom resource, but the --backend-mode command argument isnt yet exposed through the kops API, so it will still only use configmaps. We can expose a BackendMode API field in a followup PR.
ccabe51
to
32e6a6b
Compare
/test all |
/hold cancel |
/lgtm |
…-origin-release-1.16 Automated cherry pick of #8423: Update AWS IAM Authenticator to 0.5.0
…-origin-release-1.17 Automated cherry pick of #8423: Update AWS IAM Authenticator to 0.5.0
Release Notes
I merged changes from these manifests:
The new version supports replacing the ConfigMap with an IAMIdentityMapping custom resource, but the
--backend-mode
command argument isnt yet exposed through the kops API, so it will still only use configmaps. We can expose a BackendMode API field in a followup PR.Since I know you also use it...
/cc @rdrgmnzs