- 06 Jul, 2020 5 commits
-
-
Geoff Simmons authored
This introduces moving the port definitions for admin services to a headless Service -- varnish-ingress-admin in admin-svc.yaml. Services that implement Ingress with Varnish are identified by this Service: label app=varnish-ingress and at least the port named varnishadm, possibly also the admin ports for the haproxy offloader (dataplane and faccess).
-
Geoff Simmons authored
And update the "golden" files for testing generated templates.
-
Geoff Simmons authored
- Add a Unix socket listerner for the offloader. - Use VCL 4.1 (required when Unix sockets are in use).
-
Geoff Simmons authored
-
Tim Leers authored
-
- 29 Apr, 2020 15 commits
-
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Geoff Simmons authored
- The varnish controller deleted a service from its map under the wrong conditions. - Not an error if there are no Endpoints for the Service when the Delete event is synced -- they may already be gone. - Varnish and haproxy controllers delete the service from their maps before any other sync actions are taken -- otherwise error returns may prevent the deletion from ever happening. - Permanent network errors on attempts to communicate with the admin interfaces are ignored (do not cause re-queue), since the instance may be gone.
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
Tim Leers authored
-
- 17 Apr, 2020 2 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
- 07 Feb, 2020 18 commits
-
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
Starting with a pristine cluster, it initially deploys the controller and unready Services for Varnish Ingress, and verifies the deployment. Then each of the examples are deployed, verified, and undeployed. On exit the Services for Ingress and controller are undeployed, restoring the pristine state of the cluster.
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-
Geoff Simmons authored
-