-
Story
-
Resolution: Done
-
Blocker
-
None
-
None
-
None
-
False
-
None
-
False
-
Hypershift Sprint 10
-
0
-
0
-
0
Currently in OCM we use the following process to install STS clusters:
- We generate a key pair for service account signing.
- We prepare a S3 bucket with the JSON web key set and discovery documents.
- We tell the customer to create a identity provider in their account, using the URL of the S3 bucket that we prepared.
- We wait for the customer to create that identity provider.
- We verify that the identity provider is working.
- We proceed to the installation of the cluster, passing the pre-generated key pair to the OpenShift installer.
We would like to use the same process for HyperShift clusters, but currently isn't possible to pass the key pair.
This card is about adding to HyperShift the feature to receive that key pair and the pre-populated S3 bucket instead of generating them.
- blocks
-
ACM-1257 As a developr of OCM I want to be able to use `HostedCluster.spec.serviceAccountSigningKey`
- Closed
- links to