Human Connection
1.0.0
1.0.0
  • Introduction
  • Edit this Documentation
  • Installation
  • Neo4J
  • Backend
    • GraphQL
    • neo4j-graphql-js
  • Webapp
    • Components
    • HTML
    • SCSS
    • Vue
  • Testing Guide
    • End-to-end tests
    • Frontend tests
    • Backend tests
  • Contributing
  • Kubernetes Deployment
    • Minikube
    • Digital Ocean
      • Kubernetes Dashboard
      • HTTPS
    • Human Connection
      • Error Reporting
      • Mailserver
      • Maintenance
    • Volumes
      • Neo4J Offline-Backups
      • Neo4J Online-Backups
      • Volume Snapshots
      • Reclaim Policy
      • Velero
    • Metrics
    • Legacy Migration
  • Feature Specification
  • Code of conduct
  • License
Powered by GitBook
On this page
  • Configuration
  • Create a namespace
  • Create persistent volumes
  • Apply the configuration

Was this helpful?

  1. Kubernetes Deployment

Human Connection

PreviousHTTPSNextError Reporting

Last updated 5 years ago

Was this helpful?

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

Change into the ./deployment directory and copy our provided templates:

# in folder deployment/human-connection/
$ cp templates/secrets.template.yaml ./secrets.yaml
$ cp templates/configmap.template.yaml ./configmap.yaml

Change the configmap.yaml in the ./deployment/human-connection directory as needed, all variables will be available as 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 .

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

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

Create a namespace

# in folder deployment/
$ kubectl apply -f namespace.yaml

Create persistent volumes

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.

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

While the deployments and services can easily be restored, simply by deleting and applying the kubernetes configurations again, certain data is not that easily recovered. Therefore we separated persistent volumes from deployments and services. There is a . Create those persistent volumes once before you apply the configuration.

kubernetes documentation
kubernets dashboard
dedicated section