diff --git a/examples/auth/basic/haproxy/README.md b/examples/auth/basic/haproxy/README.md index f9c87b1d3..621129405 100644 --- a/examples/auth/basic/haproxy/README.md +++ b/examples/auth/basic/haproxy/README.md @@ -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 diff --git a/examples/auth/client-certs/haproxy/README.md b/examples/auth/client-certs/haproxy/README.md index 75813ff1b..b4078b4b5 100644 --- a/examples/auth/client-certs/haproxy/README.md +++ b/examples/auth/client-certs/haproxy/README.md @@ -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: diff --git a/examples/customization/custom-configuration/haproxy/README.md b/examples/customization/custom-configuration/haproxy/README.md index 708fbfae5..7763413dc 100644 --- a/examples/customization/custom-configuration/haproxy/README.md +++ b/examples/customization/custom-configuration/haproxy/README.md @@ -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. diff --git a/examples/daemonset/haproxy/README.md b/examples/daemonset/haproxy/README.md index 75fe32eb5..605af7f70 100644 --- a/examples/daemonset/haproxy/README.md +++ b/examples/daemonset/haproxy/README.md @@ -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: diff --git a/examples/deployment/haproxy/README.md b/examples/deployment/haproxy/README.md index 47e320f46..23099aded 100644 --- a/examples/deployment/haproxy/README.md +++ b/examples/deployment/haproxy/README.md @@ -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: diff --git a/examples/multi-tls/haproxy/README.md b/examples/multi-tls/haproxy/README.md index d03f4c709..bb7358c78 100644 --- a/examples/multi-tls/haproxy/README.md +++ b/examples/multi-tls/haproxy/README.md @@ -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: diff --git a/examples/rewrite/haproxy/README.md b/examples/rewrite/haproxy/README.md index 07c8fc4b3..e013bb92f 100644 --- a/examples/rewrite/haproxy/README.md +++ b/examples/rewrite/haproxy/README.md @@ -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: diff --git a/examples/scaling-deployment/haproxy/README.md b/examples/scaling-deployment/haproxy/README.md index 463550d72..748422ada 100644 --- a/examples/scaling-deployment/haproxy/README.md +++ b/examples/scaling-deployment/haproxy/README.md @@ -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: diff --git a/examples/tls-termination/haproxy/README.md b/examples/tls-termination/haproxy/README.md index e019a00ee..8f1fb8515 100644 --- a/examples/tls-termination/haproxy/README.md +++ b/examples/tls-termination/haproxy/README.md @@ -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`: