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
  • Deploy the service
  • Bring application into maintenance mode

Was this helpful?

  1. Kubernetes Deployment
  2. Human Connection

Maintenance

PreviousMailserverNextVolumes

Last updated 5 years ago

Was this helpful?

Despite our best efforts, systems sometimes require downtime for a variety of reasons.

Quote from

We use our maintenance mode for manual database backup and restore. Also we bring the database into maintenance mode for manual database migrations.

Deploy the service

We prepared sample configuration, so you can simply run:

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

This will fire up a maintenance service.

Bring application into maintenance mode

Now if you want to have a controlled downtime and you want to bring your application into maintenance mode, you can edit your global ingress server.

E.g. in file deployment/digital-ocean/https/ingress.yaml change the following:

...

  - host: nitro-staging.human-connection.org
    http:
      paths:
      - path: /
        backend:
          # serviceName: nitro-web
          serviceName: maintenance
          # servicePort: 3000
          servicePort: 80

Then run kubectl apply -f deployment/digital-ocean/https/ingress.yaml. If you want to deactivate the maintenance server, just undo the edit and apply the configuration again.

here