-
Story
-
Resolution: Done
-
Major
-
ACM 2.7.0
THE WHAT
The AWS S3 secret credential should be configurable via credentials page
THE WHY
1. This simplifies Hypershift configuration for AWS.
2. Day two password change is easier from the Console
3. Could we do some validation
Â
THE HOW (tasks)
- Add support for the AWS S3 secret. to the credentials wizard. It needs the following data:
data:
 bucket: <bucket_name>
 credentials: |
   [default]
   aws_access_key_id = <value>
   aws_secret_access_key = <value>
{{Â region: us-east-1 Â Â Â }}
- The secret should only be created in the ManagedCluster namespace on the Hub where Hypershift addon is enabled (the secret can be added after the fact)
- OPTIONAL: Maybe the Hypershift addon should add an annotation with the timestamp it reconciled at...
- causes
-
ACM-4078 S3 Bucket yaml changes do not get applied
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
- relates to
-
ACM-3901 DOC - Add support for AWS S3 credentials wizard with Hypershift
-
- Closed
-
