From 66feafa9a5e85b6feeacf22815e4fa3f4e6289f3 Mon Sep 17 00:00:00 2001 From: Richard Patel Date: Mon, 20 Apr 2020 07:29:18 +0200 Subject: [PATCH] docs: fix secret env keys on ObjectBucketClaim The documentation on the Ceph ObjectBucketClaim CRD erroneously states that the generated Secret resource contains keys `ACCESS_KEY_ID`, `SECRET_ACCESS_KEY`. According to ceph-object.md, and when mounting the secret into a container via secretRef, or inspecting it with kubectl, the variables have an `AWS_` prefix. Like so: `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`. This commit adds the `AWS_` prefix to both keys. Signed-off-by: Richard Patel --- Documentation/ceph-object-bucket-claim.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/ceph-object-bucket-claim.md b/Documentation/ceph-object-bucket-claim.md index fcd7e890d..4c8d60e5b 100644 --- a/Documentation/ceph-object-bucket-claim.md +++ b/Documentation/ceph-object-bucket-claim.md @@ -91,7 +91,7 @@ spec: ``` 1. use `env:` if mapping of the defined key names to the env var names used by the app is needed. 1. makes available to the pod as env variables: `BUCKET_HOST`, `BUCKET_PORT`, `BUCKET_NAME` -1. makes available to the pod as env variables: `ACCESS_KEY_ID`, `SECRET_ACCESS_KEY` +1. makes available to the pod as env variables: `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY` ### StorageClass ```yaml