You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Forces my-existing-secret to contain ACCESS_KEY_ID and ACCESS_SECRET_KEY.
The name of those keys are hardcoded in the template (See ACCESS_KEY_ID and ACCESS_SECRET_KEY)
This could be useful in some sceneries. For instance, when you use Rook(Ceph) to create a Bucket a secret is created with the credentials, right now isn't possible to refer to that secret because the name of the keys doesn't match with the expected by this chart.
The text was updated successfully, but these errors were encountered:
When you pass the following values:
Forces
my-existing-secret
to containACCESS_KEY_ID
andACCESS_SECRET_KEY
.The name of those keys are hardcoded in the template (See ACCESS_KEY_ID and ACCESS_SECRET_KEY)
This could be useful in some sceneries. For instance, when you use Rook(Ceph) to create a Bucket a secret is created with the credentials, right now isn't possible to refer to that secret because the name of the keys doesn't match with the expected by this chart.
The text was updated successfully, but these errors were encountered: