From 9d807a843d37087e02cd819ac0274d4c28033163 Mon Sep 17 00:00:00 2001 From: Joao Morais Date: Sun, 2 Apr 2017 09:50:52 -0300 Subject: [PATCH] Remove pre-release messages --- examples/auth/basic/haproxy/README.md | 1 - examples/auth/client-certs/haproxy/README.md | 1 - 2 files changed, 2 deletions(-) diff --git a/examples/auth/basic/haproxy/README.md b/examples/auth/basic/haproxy/README.md index 5c5edc78f..f9c87b1d3 100644 --- a/examples/auth/basic/haproxy/README.md +++ b/examples/auth/basic/haproxy/README.md @@ -11,7 +11,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 an ingress resource to the `foo.bar` domain -* Feature not on stable version; use `canary` tag As mentioned in the deployment instructions, you MUST turn down any existing ingress controllers before running HAProxy Ingress. diff --git a/examples/auth/client-certs/haproxy/README.md b/examples/auth/client-certs/haproxy/README.md index 10ec9f160..75813ff1b 100644 --- a/examples/auth/client-certs/haproxy/README.md +++ b/examples/auth/client-certs/haproxy/README.md @@ -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` * Use these same steps and create another CA and generate another certificate and private 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 ingress controllers before running HAProxy Ingress.