Implementing experimental server helm chart: 1. health and liveness probes -- • hasura supports /healthz endpoint, which I’m using for both health and liveness checks. (ok?) • graphql: apollo env variable suggests “/health” as healthcheck • apollo: doc suggests

/.well-known/apollo/server-health

• ui .. ? .. just use “/”? • towel: even more problematic, as no containerPort 2. Database password: Can I mount from secret into PGPASSWORD in environment, and leave out of HASURA_GRAPHQL_DATABASE_URL (etc)? Building “HASURA_GRAPHQL_DATABASE_URL” from secret would take a start hook (unless there is another idea?) 3. init containers • If the database doesn’t exist, it should be created using admin pass. This could be init container on hasura, I guess? • After optional db creation — what to run to create schema, if necessary? • Then there are database upgrades (alembic) — these are idempotent, right — can be run on every startup? All that can be put in hasura, I guess. For other pods, init might amount to waiting for other services to be available? If we had good health checks we could just have kubernetes kill and restart until other services were up? 4. Default database size (for pvc if not external) • 8Gi?