Bug 1896919 - start creating new-style Secrets for AWS
Summary: start creating new-style Secrets for AWS
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Credential Operator
Version: 4.6.z
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.z
Assignee: Joel Diaz
QA Contact: wang lin
Depends On: 1896918
TreeView+ depends on / blocked
Reported: 2020-11-11 20:47 UTC by Joel Diaz
Modified: 2021-02-08 13:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1896918
Last Closed: 2021-02-08 13:50:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cloud-credential-operator pull 268 0 None closed Bug 1896919: [release-4.6] add new credentials field for AWS Secrets 2021-02-05 18:32:32 UTC
Red Hat Product Errata RHSA-2021:0308 0 None None None 2021-02-08 13:51:05 UTC

Description Joel Diaz 2020-11-11 20:47:30 UTC
+++ This bug was initially created as a clone of Bug #1896918 +++

Description of problem:
Going forward, CCO needs to create Secrets containing AWS credentials/configuration into a new 'credentials' field in the Secret.
It must continue to populate the legacy aws_access_key_id and aws_secret_access_key, but it will now build a valid AWS configuration file with the same credentials information:

aws_access_key_id = ACCESSKEY
aws_secret_access_key = secretkey

Comment 6 errata-xmlrpc 2021-02-08 13:50:51 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.6.16 security and bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.