Skip to content
This repository has been archived by the owner on Mar 22, 2024. It is now read-only.

Improve Tornjak documentation #439

Merged
merged 1 commit into from
Aug 16, 2023
Merged
Changes from all commits
Commits
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
7 changes: 6 additions & 1 deletion examples/tornjak/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ helm upgrade --install --namespace spire-server \
--values ../production/values.yaml \
--values ./values.yaml \
--render-subchart-notes \
spire charts/spire
spire ../../charts/spire

# test the Tornjak deployment
helm test spire -n spire-server
Expand All @@ -27,8 +27,13 @@ To access Tornjak you will have to use port-forwarding for the time being *(unti

Run following commands from your shell, if you ran with different values your namespace might differ. Consult the install notes printed when running above `helm upgrade` command in that case.

Since `port-forward` is a blocking command, execute them in two different consoles:

```shell
kubectl -n spire-server port-forward service/spire-tornjak-backend 10000:10000
```

```shell
kubectl -n spire-server port-forward service/spire-tornjak-frontend 3000:3000
```

Expand Down