Skip to content

feat(helm): add GKE ManagedCertificate support for automatic TLS#1580

Merged
chocobar merged 1 commit intomainfrom
helm-goodness
Feb 5, 2026
Merged

feat(helm): add GKE ManagedCertificate support for automatic TLS#1580
chocobar merged 1 commit intomainfrom
helm-goodness

Conversation

@chocobar
Copy link
Collaborator

@chocobar chocobar commented Feb 5, 2026

Summary

  • Adds optional support for Google-managed TLS certificates on GKE deployments
  • When enabled, the Helm chart automatically creates a ManagedCertificate resource
  • Eliminates the need for manual certificate setup when deploying to GKE with a custom domain

Usage

In values.yaml:

ingress:
  enabled: true
  className: "gce"
  annotations:
    kubernetes.io/ingress.global-static-ip-name: "helix-ip"
    networking.gke.io/managed-certificates: "my-helix-controlplane-managed-cert"
  hosts:
    - host: helix.example.com
      paths:
        - path: /
          pathType: Prefix
  gke:
    managedCertificate:
      enabled: true

Test plan

  • Deploy to GKE with ingress.gke.managedCertificate.enabled: true
  • Verify ManagedCertificate resource is created
  • Verify certificate provisions successfully (takes 10-15 min)
  • Verify HTTPS works on the domain

🤖 Generated with Claude Code

Adds optional support for Google-managed TLS certificates on GKE deployments.
When enabled, the Helm chart automatically creates a ManagedCertificate
resource, eliminating the need for manual certificate setup.

Usage in values.yaml:
  ingress:
    enabled: true
    gke:
      managedCertificate:
        enabled: true

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@chocobar chocobar merged commit 5a3cec5 into main Feb 5, 2026
9 checks passed
@chocobar chocobar deleted the helm-goodness branch February 5, 2026 12:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant