Skip to content
This repository has been archived by the owner on Apr 17, 2019. It is now read-only.

v0.6.3: GCE L7 Ingress controller [beta]
Compare
Choose a tag to compare
@bprashanth bprashanth released this 08 Jun 18:50
· 2109 commits to master since this release
0.6.3
1ec21d8

Image: gcr.io/google_containers/glbc:0.6.3
Changelog:

  • Stability fixes: Improve reliability of GCE client creation/Url map updates etc
  • Controller UID: The ingress controller allocates UIDs so 2 kubernetes clusters in the same gce project, with the same ingress, don't collide.
  • TLS Certificates: Certificates are updated in GCE when Kubernetes secrets change.
  • Firewall rules: The single firewall rule required to allow L7 health checks is created and synced automatically by the controller.

Getting Started:
Kick the tires by creating an ingress. You can also perform a dry run on any machine where kubectl works against a Kubernetes cluster by invoke the release binary with glbc --running-in-cluster=false. A dry run will not create any cloud resources.

Make sure you satisfy the pre-requisites, consult these docs for troubleshooting and see the wishlist if you'd like to contribute to the next release.

Assets 3
Loading