mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-14 08:02:15 +03:00

History

hasura-bot 53d5fc9cea add liveness and readiness kubernetes probes GITHUB_PR_NUMBER: 9357 GITHUB_PR_URL: https://github.com/hasura/graphql-engine/pull/9357 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/7455 Co-authored-by: Antoine Pultier <45740+fungiboletus@users.noreply.github.com> GitOrigin-RevId: 01f3a95fd607724ea29a83ebe85ae544045be17f		2023-02-15 15:13:26 +00:00
..
deployment.yaml	add liveness and readiness kubernetes probes	2023-02-15 15:13:26 +00:00
README.md	add installation manifests (#432 )	2018-09-13 15:03:13 +05:30
svc.yaml	add installation manifests (#432 )	2018-09-13 15:03:13 +05:30

README.md

Deploy Hasura GraphQL engine on Kubernetes

Step 1: Edit deployment.yaml and set the right database url

...
        env:
        - name: HASURA_GRAPHQL_DATABASE_URL
          value: postgres://username:password@hostname:port/dbname
...

Step 2: Create the kubernetes deployment, service

kubectl create -f deployment.yaml
kubectl create -f svc.yaml

Step 3: Access the console

This creates a LoadBalancer type service with port 80. So you should be able to access the console at the external IP.

For example, using docker-for-desktop on mac:

$ kubectl get svc
NAME         TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)        AGE
hasura       LoadBalancer   10.96.214.240   localhost     80:30303/TCP   4m
kubernetes   ClusterIP      10.96.0.1       <none>        443/TCP        8m

Head to: http://localhost and the console should load!