Skip to content

Commit

Permalink
docs: make installation instructions clearer
Browse files Browse the repository at this point in the history
  • Loading branch information
psanders committed Sep 12, 2023
1 parent 8f447ff commit f79c1a9
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
6 changes: 3 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -170,19 +170,19 @@ helm repo update
Then, create a namespace for Routr:

```bash
kubectl create namespace sipnet
kubectl create namespace routr
```

Next, install Routr with the following command:

```bash
helm install sipnet routr/routr-connect --namespace sipnet
helm install my-release routr/routr-connect --namespace routr
```

Finally, wait a few minutes for the pods to start. You can check the status of the pods with the following command:

```bash
kubectl get pods -n sipnet
kubectl get pods -n routr
```

You should see a list of pods and their status. If the status is Running, then you are ready to go.
Expand Down
6 changes: 3 additions & 3 deletions ops/charts/connect/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Website: https://routr.io
```bash
$ helm repo add routr https://routr.io/charts
$ helm repo update
$ helm install routr routr/routr
$ helm install routr routr/routr-connect
```

**Note**: `routr` is your release name.
Expand All @@ -36,10 +36,10 @@ To install the chart with the release name my-release:

```bash
$ kubectl create namespace routr
$ helm install my-release routr/routr --namespace routr
$ helm install my-release routr/routr-connect --namespace routr
```

The command deploys Routr Server in the `default` namespace on the Kubernetes cluster in the default configuration.
The command deploys Routr Server in the `routr` namespace on the Kubernetes cluster in the default configuration.

We recommend using a namespace for easy upgrades.

Expand Down

0 comments on commit f79c1a9

Please sign in to comment.