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

Jump to bottom

Update the mTLS secret name #290

Merged
merged 1 commit into from
Jul 17, 2023
Merged

Update the mTLS secret name #290

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
6 changes: 3 additions & 3 deletions examples/tls_mtls/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ tls.key
For mTLS we will additionally need to deliver a user CA certificate to the Tornjak container. Currently it is found at `CA-user/rootCA.crt`. The process is the same. First we create the secret:

```
kubectl create secret generic -n spire tornjak-user-certs \
kubectl create secret generic -n spire tornjak-user-ca \
--from-file=CA-user/rootCA.crt
```

Expand All @@ -134,7 +134,7 @@ volumes:
secretName: tornjak-server-tls
- name: user-cas
secret:
secretName: tornjak-user-certs
secretName: tornjak-user-ca
items:
- key: rootCA.crt
path: userCA.crt
Expand Down Expand Up @@ -282,7 +282,7 @@ curl --cacert CA-server/rootCA.crt https://<Tornjak_TLS_endpoint>

In order to make a TLS call we need only a CA certificate that can validate the certificate/key pair given to Tornjak in step 1. In our case, we can use the certificate within `CA-server`.

Additionally, we must have a certificate/key pair locally that was signed by the CA certificate given to the Tornjak server via `tornjak-user-certs` secret when configuring mTLS. In our case, we can use the certificate/key pair `user.crt` and `user.key`:
Additionally, we must have a certificate/key pair locally that was signed by the CA certificate given to the Tornjak server via `tornjak-user-ca` secret when configuring mTLS. In our case, we can use the certificate/key pair `user.crt` and `user.key`:

```
curl --cacert CA-server/rootCA.crt --key user.key --cert user.crt https://<Tornjak_mTLS_endpoint>
Expand Down
Loading