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

Remove pre-release messages

Browse source
This commit is contained in:
Joao Morais 2017-04-02 09:50:52 -03:00
parent 02cd3ce885
commit 9d807a843d
2 changed files with 0 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -11,7 +11,6 @@ This document has the following prerequisites:
* Deploy [HAProxy Ingress controller](/examples/deployment/haproxy), you should * Deploy [HAProxy Ingress controller](/examples/deployment/haproxy), you should
end up with controller, a sample web app and an ingress resource to the `foo.bar` end up with controller, a sample web app and an ingress resource to the `foo.bar`
domain domain
* Feature not on stable version; use `canary` tag
As mentioned in the deployment instructions, you MUST turn down any existing As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress. ingress controllers before running HAProxy Ingress.

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

@ -16,7 +16,6 @@ following these steps you should have a secret named `caingress`, a certificate
`client.crt` and it's private key `client.key` `client.crt` and it's private key `client.key`
* Use these same steps and create another CA and generate another certificate and private * Use these same steps and create another CA and generate another certificate and private
key `fake.crt` and `fake.key` just for testing key `fake.crt` and `fake.key` just for testing
* Feature not on stable version yet; use `canary` tag
As mentioned in the deployment instructions, you MUST turn down any existing As mentioned in the deployment instructions, you MUST turn down any existing
ingress controllers before running HAProxy Ingress. ingress controllers before running HAProxy Ingress.