Consequently create another template folder

... in human-connection/ where we store our specific kubernetes
configuraitons.
This commit is contained in:
Robert Schäfer 2019-05-15 13:55:18 +02:00
parent 24fe55c2d5
commit d70719040e
4 changed files with 13 additions and 4 deletions

View File

@ -9,13 +9,21 @@ just apply our provided configuration files to your cluster.
Copy our provided templates: Copy our provided templates:
```bash ```bash
$ cp secrets.template.yaml human-connection/secrets.yaml # in folder deployment/human-connection/
$ cp configmap.template.yaml human-connection/configmap.yaml $ cp templates/secrets.template.yaml ./secrets.yaml
$ cp templates/configmap.template.yaml ./configmap.yaml
``` ```
Change the `configmap.yaml` as needed, all variables will be available as Change the `configmap.yaml` as needed, all variables will be available as
environment variables in your deployed kubernetes pods. environment variables in your deployed kubernetes pods.
Probably you want to change this environment variable to your actual domain:
```
# in configmap.yaml
CLIENT_URI: "https://nitro-staging.human-connection.org"
```
If you want to edit secrets, you have to `base64` encode them. See [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-manually). If you want to edit secrets, you have to `base64` encode them. See [kubernetes documentation](https://kubernetes.io/docs/concepts/configuration/secret/#creating-a-secret-manually).
```bash ```bash
@ -30,7 +38,8 @@ your deployed kubernetes pods.
## Create a namespace ## Create a namespace
```bash ```bash
$ kubectl apply -f namespace-human-connection.yaml # in folder deployment/human-connection/
$ kubectl apply -f namespace.yaml
``` ```
If you have a [kubernets dashboard](../digital-ocean/dashboard/README.md) If you have a [kubernets dashboard](../digital-ocean/dashboard/README.md)