Skip to content

doc: change "associate" to "create" for OpenID connector #1208

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

Merged
merged 6 commits into from
Jan 8, 2020
Merged

doc: change "associate" to "create" for OpenID connector #1208

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
b4c0696
Changing associate to create for open ID connector
goswamig Jan 6, 2020
445aa41
Matching the width with header
goswamig Jan 6, 2020
9d64d0d
Rewording the sentence
goswamig Jan 6, 2020
ccd1908
Reword the sentence for OIDC
goswamig Jan 6, 2020
74e6b5e
Addressing comment
goswamig Jan 6, 2020
51635a0
Merge branch 'master' into master
laurenyu Jan 8, 2020
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
9 changes: 4 additions & 5 deletions doc/amazon_sagemaker_operators_for_kubernetes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,12 +82,11 @@ IAM role-based operator deployment
Before you can deploy your operator using an IAM role, associate an OpenID Connect (OIDC) provider with your role to
authenticate with the IAM service.

Associate an OpenID Connect Provider to Your Instance
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create an OpenID Connect Provider for Your Cluster
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

Create an OIDC identity provider for your cluster. If your
cluster is managed by EKS, then your cluster will already have an OIDC
attached to it.
The following instruction will create and associate an OIDC provider
with your EKS cluster.

Set the local ``CLUSTER_NAME`` and \ ``AWS_REGION`` environment
variables as follows:
Expand Down