Skip to content

Commit 30c5248

Browse files
author
Aaron Schlesinger
committed
doc(object-storage): note that the controller uses the minio-user secret even if not using minio
1 parent 9acce65 commit 30c5248

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

src/installing-workflow/configuring-object-storage.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ The controller needs no environment variables for object storage configuration.
100100

101101
### Credentials
102102

103-
Since the object storage location information comes from the builder, the controller only needs access to the credentials information. The controller gets this information by accessing the `minio-user` secret directly from the Kubernetes API.
103+
Since the object storage location information comes from the builder, the controller only needs access to the credentials information. The controller gets this information by accessing the `minio-user` secret (even if it's not using Minio as the object storage system) directly from the Kubernetes API.
104104

105105
No paths need to be mounted into the pod. Simply ensure that the secret exists in your Kubernetes cluster with the correct credentials.
106106

0 commit comments

Comments
 (0)