DevFW-CICD/ingress-nginx-helm
16
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

modified docs

Browse source
This commit is contained in:
Nick Sardo 2017-04-12 16:21:35 -07:00
parent 6c4fe22df4
commit ce5257d9a7
4 changed files with 4 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
controllers/gce/backends/backends.go
View file

@ -224,11 +224,6 @@ func newBackendService(igs []*compute.InstanceGroup, bm BalancingMode, namedPort
} }
} }
func (b *Backends) updateProtocol(bs *compute.BackendService, hcLink string, protocol utils.AppProtocol) (*compute.BackendService, error) {
return bs, nil
}
// Add will get or create a Backend for the given port. // Add will get or create a Backend for the given port.
func (b *Backends) Add(p ServicePort) error { func (b *Backends) Add(p ServicePort) error {
// We must track the port even if creating the backend failed, because // We must track the port even if creating the backend failed, because

4
controllers/gce/controller/utils.go
View file

@ -559,8 +559,8 @@ func (t *GCETranslator) getHTTPProbe(svc api_v1.Service, targetPort intstr.IntOr
continue continue
} }
for _, p := range c.Ports { for _, p := range c.Ports {
if targetPort.Type == intstr.Int && targetPort.IntVal == p.ContainerPort || if (targetPort.Type == intstr.Int && targetPort.IntVal == p.ContainerPort) ||
targetPort.Type == intstr.String && targetPort.StrVal == p.Name { (targetPort.Type == intstr.String && targetPort.StrVal == p.Name) {
readinessProbePort := c.ReadinessProbe.Handler.HTTPGet.Port readinessProbePort := c.ReadinessProbe.Handler.HTTPGet.Port
switch readinessProbePort.Type { switch readinessProbePort.Type {

4
controllers/gce/examples/health_checks/README.md
View file

@ -67,8 +67,6 @@ You can confirm the health check endpoint point it's using one of 2 ways:
A few points to note: A few points to note:
* The readiness probe must be exposed on the port matching the `servicePort` specified in the Ingress * The readiness probe must be exposed on the port matching the `servicePort` specified in the Ingress
* The readiness probe cannot have special requirements, like headers or HTTPS * The readiness probe cannot have special requirements like headers
* The probe timeouts are translated to GCE health check timeouts * The probe timeouts are translated to GCE health check timeouts
* You must create the pods backing the endpoints with the given readiness probe. This *will not* work if you update the replication controller with a different readiness probe. * You must create the pods backing the endpoints with the given readiness probe. This *will not* work if you update the replication controller with a different readiness probe.

4
examples/health-checks/gce/README.md
View file

@ -67,8 +67,6 @@ You can confirm the health check endpoint point it's using one of 2 ways:
A few points to note: A few points to note:
* The readiness probe must be exposed on the port matching the `servicePort` specified in the Ingress * The readiness probe must be exposed on the port matching the `servicePort` specified in the Ingress
* The readiness probe cannot have special requirements, like headers or HTTPS * The readiness probe cannot have special requirements like headers
* The probe timeouts are translated to GCE health check timeouts * The probe timeouts are translated to GCE health check timeouts
* You must create the pods backing the endpoints with the given readiness probe. This *will not* work if you update the replication controller with a different readiness probe. * You must create the pods backing the endpoints with the given readiness probe. This *will not* work if you update the replication controller with a different readiness probe.