ocelot-Social-Community/Ocelot-Social
1
0
Fork 0
mirror of https://github.com/Ocelot-Social-Community/Ocelot-Social.git synced 2025-12-12 23:35:58 +00:00
Code Issues Packages Projects Releases Wiki Activity
Ocelot-Social/deployment/human-connection/README.md
Robert Schäfer 7f2df14ef3 Update human connection specific configuration
2019-04-24 12:52:10 +02:00

1.5 KiB
Raw Blame History

Kubernetes Configuration for Human Connection

Deploying Human Connection with kubernetes is straight forward. All you have to do is to change certain parameters, like domain names and API keys, then you just apply our provided configuration files to your cluster.

Configuration

Copy our provided templates:

$ cp secrets.template.yaml human-connection/secrets.yaml
$ cp configmap.template.yaml human-connection/configmap.yaml

Change the configmap.yaml as needed, all variables will be available as environment variables in your deployed kubernetes pods.

If you want to edit secrets, you have to base64 encode them. See kubernetes documentation.

# example how to base64 a string:
$ echo -n 'admin' | base64 --wrap 0
YWRtaW4=

Those secrets get base64 decoded and are available as environment variables in your deployed kubernetes pods.

Create a namespace

$ kubectl apply -f namespace-human-connection.yaml

If you have a kubernets dashboard deployed you should switch to namespace human-connection in order to monitor the state of your deployments.

Apply the configuration

# in folder deployment/ 
$ kubectl apply -f human-connection/

This can take a while because kubernetes will download the docker images. Sit back and relax and have a look into your kubernetes dashboard. Wait until all pods turn green and they don't show a warning Waiting: ContainerCreating anymore.