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

Merge pull request #1251 from jcmoraisjr/jm-haproxy-ingress-class

Browse source 
Add ingress.class support to HAProxy Ingress
This commit is contained in:
Manuel Alejandro de Brito Fontes 2017-08-27 20:57:14 -04:00 committed by GitHub
commit 69c89ccfdd
9 changed files with 12 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
examples/auth/basic/haproxy/README.md
View file

@ -12,9 +12,6 @@ This document has the following prerequisites:
end up with controller, a sample web app and an ingress resource to the `foo.bar`
domain
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
## Using Basic Authentication
HAProxy Ingress read user and password from `auth` file stored on secrets, one user

3
examples/auth/client-certs/haproxy/README.md
View file

@ -17,9 +17,6 @@ following these steps you should have a secret named `caingress`, a certificate
* Use these same steps and create another CA and generate another certificate and private
key `fake.crt` and `fake.key` just for testing
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
Secret, certificates and keys can be created using these shortcuts:
CA and it's secret:

3
examples/customization/custom-configuration/haproxy/README.md
View file

@ -8,9 +8,6 @@ This document has the following prerequisites:
Deploy only the tls-secret and the default backend from the [deployment instructions](../../../deployment/haproxy/)
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
## Customize the HAProxy configuration
Using a [ConfigMap](https://kubernetes.io/docs/user-guide/configmap/) is possible to customize the HAProxy configuration.

8
examples/daemonset/haproxy/README.md
View file

@ -4,10 +4,10 @@ In some cases, the Ingress controller will be required to be run at all the node
## Prerequisites
This ingress controller doesn't yet have support for
[ingress classes](/examples/PREREQUISITES.md#ingress-class). You MUST turn
down any existing ingress controllers before running HAProxy Ingress controller or
they will fight for Ingresses. This includes any cloudprovider controller.
If you have another Ingress controller deployed, you will need to make sure your
Ingress resources target exactly one Ingress controller by specifying the
[ingress.class](/examples/PREREQUISITES.md#ingress-class) annotation as
`haproxy`.
This document has also the following prerequisites:

8
examples/deployment/haproxy/README.md
View file

@ -5,10 +5,10 @@ for instructions on how to create a new one.
## Prerequisites
This ingress controller doesn't yet have support for
[ingress classes](/examples/PREREQUISITES.md#ingress-class). You MUST turn
down any existing ingress controllers before running HAProxy Ingress controller or
they will fight for Ingresses. This includes any cloudprovider controller.
If you have another Ingress controller deployed, you will need to make sure your
Ingress resources target exactly one Ingress controller by specifying the
[ingress.class](/examples/PREREQUISITES.md#ingress-class) annotation as
`haproxy`.
This document has also the following prerequisites:

3
examples/multi-tls/haproxy/README.md
View file

@ -9,9 +9,6 @@ This document has the following prerequisites:
* Deploy [HAProxy Ingress controller](/examples/deployment/haproxy), you should end up with controller, a sample web app and default TLS secret
* Create [*two* secrets](/examples/PREREQUISITES.md#tls-certificates) named `foobar-ssl` with subject `'/CN=foo.bar'` and `barfoo-ssl` with subject `'/CN=bar.foo'`
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
## Using a new TLS certificate
Update ingress resource in order to add TLS termination to two hosts:

3
examples/rewrite/haproxy/README.md
View file

@ -12,9 +12,6 @@ the `foo.bar` domain
* Configure only the default [TLS termination](/examples/tls-termination/haproxy) -
there is no need to create another secret
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
## Annotations
The following annotations are implemented:

8
examples/scaling-deployment/haproxy/README.md
View file

@ -4,10 +4,10 @@ This example aims to demonstrate the Deployment of multi haproxy ingress control
## Prerequisites
This ingress controller doesn't yet have support for
[ingress classes](/examples/PREREQUISITES.md#ingress-class). You MUST turn
down any existing ingress controllers before running HAProxy Ingress controller or
they will fight for Ingresses. This includes any cloudprovider controller.
If you have another Ingress controller deployed, you will need to make sure your
Ingress resources target exactly one Ingress controller by specifying the
[ingress.class](/examples/PREREQUISITES.md#ingress-class) annotation as
`haproxy`.
This document has also the following prerequisites:

3
examples/tls-termination/haproxy/README.md
View file

@ -7,9 +7,6 @@ This document has the following prerequisites:
* Deploy [HAProxy Ingress controller](/examples/deployment/haproxy), you should end up with controller, a sample web app and default TLS secret
* Create [*another* secret](/examples/PREREQUISITES.md#tls-certificates) named `foobar-ssl` and subject `'/CN=foo.bar'`
As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress.
## Using default TLS certificate
Update ingress resource in order to add TLS termination to host `foo.bar`: