-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
MCE 2.2.0, ACM 2.7.0
-
Align AWS-Gov Credential secrets for ClusterDeployment with the HiveConfig credential secret
-
False
-
None
-
False
-
Not Selected
-
To Do
Description of problem:
In order to deploy an aws-gov from ACM, hive requires use of AWS Private Link. In order to do this, we need to update HiveConfig with an aws-gov credential secret that can do what private link does... but when we create the ClusterDeployment, we also need to set a credential to create the cluster (this can be in any namespace).
Example HiveConfig snippet:
spec: awsPrivateLink: associatedVPCs: - credentialsSecretRef: name: clc-aws-cred region: us-gov-east-1 vpcID: vpc-0d0db3e664ee45657 credentialsSecretRef: name: clc-aws-cred dnsRecordType: ARecord endpointVPCInventory: - region: us-gov-east-1 subnets: - availabilityZone: us-gov-east-1a subnetID: subnet-00bf8fcc779ac848a - availabilityZone: us-gov-east-1b subnetID: subnet-05ee95537be0a8e71 - availabilityZone: us-gov-east-1c subnetID: subnet-0de5d0193103a0683 vpcID: vpc-05ac209956ba057c5
We should ensure this secret is in hive namespace so user only requires to create secret once.
Also, if the secret does not exist in hive namespace, but we provide one for the CD, the error will never bubble up to ACM CD, we have to check the hive logs in order to find the issue. We should get this error so user knows what to fix.
Version-Release number of selected component (if applicable):
ACM 2.7.0-FC1
How reproducible:
always
Steps to Reproduce:
- ...