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.

Sign up for GitHub

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

Remove deprecated language from README #244

Merged
merged 1 commit into from
Jul 10, 2019
Merged

Remove deprecated language from README #244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ systemctl restart kubelet.service

### Configure IAMIdentityMapping Custom Resource Definitions

In the `master` version of the AWS IAM Authenticator you can configure your users using one of two methods. The deprecated `mapUsers` and `mapRoles` as seen in the [Full Configuration Format](#full-configuration-format) or using [Kubernetes Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). This method allows the authenticator server to always stay upto date with the latest allowed user. See [Issues #79](https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/79) for more details.
In the `master` version of the AWS IAM Authenticator you can configure your users using one of two methods. The `mapUsers` and `mapRoles` as seen in the [Full Configuration Format](#full-configuration-format) or using the new (alpha) [Kubernetes Custom Resource Definitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/). This method allows the authenticator server to always stay upto date with the latest allowed user. See [Issues #79](https://github.com/kubernetes-sigs/aws-iam-authenticator/issues/79) for more details.

To setup an `IAMIdentityMapping` CRD you'll first need to `apply` the CRD manifest:

Expand Down Expand Up @@ -347,8 +347,6 @@ server:
# role to assume before querying EC2 API in order to discover metadata like EC2 private DNS Name
ec2DescribeInstancesRoleARN: arn:aws:iam::000000000000:role/DescribeInstancesRole

# DEPRECATED: Going forward these roles will be defined using Custom
# Resource definitions. See above Custom Resource Definitions for more info.
# each mapRoles entry maps an IAM role to a username and set of groups
# Each username and group can optionally contain template parameters:
# 1) "{{AccountID}}" is the 12 digit AWS ID.
Expand Down Expand Up @@ -392,8 +390,6 @@ server:
groups:
- system:masters

# DEPRECATED: Going forward these roles will be defined using Custom
# Resource definitions. See above Custom Resource Definitions for more info.
# each mapUsers entry maps an IAM role to a static username and set of groups
mapUsers:
# map user IAM user Alice in 000000000000 to user "alice" in group "system:masters"
Expand Down