Skip to content

Instantly share code, notes, and snippets.

@danielrosehill
Created April 22, 2024 03:38
Show Gist options
  • Select an option

  • Save danielrosehill/9f03e1247364227f9a4318a0a5f7783c to your computer and use it in GitHub Desktop.

Select an option

Save danielrosehill/9f03e1247364227f9a4318a0a5f7783c to your computer and use it in GitHub Desktop.
Self Hosting Metabase Community Edition On Google Kubernetes Engine (GKE)

Validated as "possible" on today's date (22/04/24).

-> Create a project -> Enable the GKE API / get access -> Deploy 2 containers (metabase/metabase:official and postgres) -> Put the environment variables under the containers -> Deploy the workload. GKE will assign the resources. -> Finally, create an ingress route and port forward from the load balancer (TCP 80) onto port 3000 which is what Metabase listens on for connections -> To my amazement, it's running!

image image

The workload spun up a few pods. As it's a 2 container architecture it's easy to tell the two resources apart:

image

GKE will take the environment variables that you entered and gather them into a secrets file that you can inspect

image

To set the port forwarding on the load balancer I needed to edit the file by hand:

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment