hasura / helm-charts

A repository for Hasura GraphQL Engine helm charts

Hasura Helm Charts

This repository contains Helm charts to help with the deployment of Hasura GraphQL on Kubernetes. This project is currently in active development.

Repository

The Charts are available in a Helm Chart Repository. Helm must be installed to use these charts. Please refer to the official documentation to get started.

helm repo add hasura https://hasura.github.io/helm-charts/
helm repo update

You can then see the charts by running:

helm search repo hasura

You can change the repo name hasura to another one if getting conflicts.

For more information, have a look at the Using Helm documentation.

Contributing

Check out our contributing guide for more details.

License

Resources in this repository are released under the Apache 2.0 license.

helm-charts's Issues

Can not create Ingress Controller

Hello, I can't get the Ingress Controller to work. I'm on Docker Desktop on Windows with enabled Kubernetes.
And I use the nginx Ingres Controller.

This is my values.yaml File:

ingress:
  enabled: true
  hostName: "hasura.docker.internal"
  ingressClassName: "nginx"
  annotations: {}

postgres:
  enabled: true

  auth:
    username: postgres
    password: postgrespassword
    database: postgres

  persistence:
    enabled: true
    size: 1Gi

secret:
  adminSecret: "my-secret"
  jwtSecret: {"type": "HS256", "key": "this-is-a-generic-HS256-secret-key-and-you-should-really-change-it"}
  unauthorizedRole: "anonymous"
  extraSecrets:
    DATA_DATABASE_URL: postgres://postgres:postgrespassword@postgres:5432/postgres

extraEnvs:
  - name: JWT_URL
    value: http://hasura-jwt:3000

The following command was used: helm upgrade hasura -f ./values.yaml hasura/hasura-enterprise-stack

I also tried to add my own Ingress:

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: nginx-ingress
spec:
  ingressClassName: nginx
  rules:
    - host: hasura.docker.internal
      http:
        paths:
          - path: /
            pathType: "ImplementationSpecific"
            backend:
              service:
                name: hasura-graphql-engine
                port:
                  number: 8080

With this, I'm able to get the Hasura login site, but then I get 401 Unauthorized Error after login.

Setting `serviceAccount.enabled: true` does not create a service account

When setting the serviceAccount.enabled field in the values.yaml for the graphql-engine chart, this sets the field in the deployment.yaml to use that service account name, but doesn't create a service account (there isn't a service account template in the chart)

serviceAccount:
    enabled: false # or true
    name: ""

ideally this would create the service account to be used by the graphql-engine deployment