Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix for custom TLS certificates docs #934

Merged
merged 1 commit into from
Dec 20, 2021
Merged

Fix for custom TLS certificates docs #934

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/examples.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ This example will deploy a MinIO tenant with TLS using certificates provided by
### Prerequisites

- You can generate certificates using `Vault CA`, `Openssl` or `Mkcert`, for this example we will use https://github.com/FiloSottile/mkcert
- Assuming your Tenant name will be `minio` you should generate the following certificate keypairs:
- Assuming your Tenant name is `storage` and your namespace is `minio-tenant` you should generate the following certificate keypairs:

```sh
mkcert "*.minio-tenant.svc.cluster.local"
Expand Down Expand Up @@ -106,6 +106,7 @@ You can deploy a preconfigured example by running the following command:
```$xslt
kustomize build examples/kustomization/base | kubectl apply -f -
```
You can include all the certificates that you want in your Tenant and `MinIO` will serve them to its client via [SNI](https://en.wikipedia.org/wiki/Server_Name_Indication)

## MinIO Tenant with TLS via customer provided certificates and Encryption enabled via Vault KMS

Expand Down