feedc0de/my-rook-config
1
0 Fork 0
forked from rook/rook
Code Pull Requests Activity

docs: fix secret env keys on ObjectBucketClaim

Browse Source 
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 <me@terorie.dev>
This commit is contained in:
Richard Patel committed 2020-04-20 23:37:44 +02:00
1 parent 56cd128eef
commit 66feafa9a5
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
Documentation/ceph-object-bucket-claim.md
+1 -1
View File
@@ -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