Shepherd
  • Introduction to Shepherd
  • Deployment
    • Creating the Helm Chart
    • Deploy to EKS on AWS
    • Deploy to GKE on GCP
    • Deploy to AKS on Azure
  • Managed Upgrades
  • [Coming Soon] Break-Glass Debugging
Powered by GitBook
On this page
  • Features
  • Certificates for External Ingress
  1. Deployment

Deploy to GKE on GCP

PreviousDeploy to EKS on AWSNextDeploy to AKS on Azure

Last updated 5 months ago

Shepherd generated Helm charts can easily be deployed on GKE in GCP. To use some features of Kubernetes your cluster must comply with a few requirements.

Features

Certificates for External Ingress

Shepherd Helm charts can automatically set up externally facing ingress with signed certificates on your domain on GCP. To use this feature, install your Helm chart to your GKE cluster as normal. Once the pods have been provisioned on your cluster, view the ingress resource that has been provisioned on your cluster and note the IP address assigned to the load balancer.

Once you have this IP, create an A record in the DNS provider for your domain that points at this IP. The certificate will be automatically provisioned by GCP once the A record has been added. It may take 1-2 hours for this certificate provisioning to complete.

Internet-facing ingress provisioned for a Shepherd Helm chart