Skip to content

Commit 238d088

Browse files
committed
recitfying story 2
1 parent 5e2b156 commit 238d088

File tree

1 file changed

+3
-3
lines changed
  • enhancements/sig-architecture/105-aws-iam-registration

1 file changed

+3
-3
lines changed

enhancements/sig-architecture/105-aws-iam-registration/README.md

+3-3
Original file line numberDiff line numberDiff line change
@@ -52,11 +52,11 @@ It must be possible for the cluster administrator to specify they wish to authen
5252
```
5353

5454

55-
#### Story 2 - EKS Hub administrator must initialize a hub using aws-irsa authentication strategy only, using csr authentication strategy will throw an error
55+
#### Story 2 - Hub administrator can initialize a hub using aws-irsa authentication strategy or CSR based authentication.
5656

57-
`clusteradm init` command must fail if the EKS hub admin tries to initialize the hub, using `csr` authentication or, by leaving it at its default setting.
57+
`clusteradm init` command will be using `csr` authentication by default.
5858

59-
`clusteradm init` can check this by creating a dummy CSR (Certificate Signing Request), attempting to approve it, and checking if it succeeds or fails and finally deleting CSR. If client CSR authentication is not available for the hub cluster, the CSR will receive a "failed" condition.
59+
The `clusteradm init` command can verify CSR (Certificate Signing Request) support by creating a dummy CSR, attempting to approve it, and checking the outcome. If client CSR authentication is unavailable for the hub cluster, the dummy CSR will receive a "failed" condition, and the administrator will receive a warning.
6060

6161
OCM hub will support following authentication strategies:
6262
- **aws-irsa** (supported only when both hub and managed cluster are on EKS)

0 commit comments

Comments
 (0)