update to v0.14.0-alpha.1

README.md

@@ -22,6 +22,7 @@ Updates made to the cluster are applied on the fly to the HAProxy instance.
 
 | HAProxy Ingress                                      | Embedded<br/>HAProxy | Supported<br/>Kubernetes | External<br/>HAProxy (*) |
 |------------------------------------------------------|----------------------|--------------------------|--------------------------|
+| [`v0.14`](CHANGELOG/CHANGELOG-v0.14.md) **(alpha)**  | `2.4`                | `1.19+`                  | `2.2` - `2.4`            |
 | [`v0.13`](CHANGELOG/CHANGELOG-v0.13.md) **(latest)** | `2.3`                | `1.19+`                  | `2.2` - `2.4`            |
 | [`v0.12`](CHANGELOG/CHANGELOG-v0.12.md)              | `2.2`                | `1.18` - `1.21`          | `2.0` - `2.4`            |
 | [`v0.10`](CHANGELOG/CHANGELOG-v0.10.md)              | `2.0`                | `1.8` - `1.21`           | -                        |

docs/config.toml

@@ -1,4 +1,4 @@
-baseURL = "/v0.13"
+baseURL = "/v0.14"
 title = "HAProxy Ingress"
 
 enableRobotsTXT = true
@@ -81,12 +81,16 @@ privacy_policy = ""
 
 # Menu title if your navbar has a versions selector to access old versions of your site.
 # This menu appears only if you have at least one [params.versions] set.
-version_menu = "v0.13"
+version_menu = "v0.14"
 
 [[params.versions]]
 version = "Latest"
 url = "https://haproxy-ingress.github.io/docs"
 
+[[params.versions]]
+version = "v0.14"
+url = "https://haproxy-ingress.github.io/v0.14/docs"
+
 [[params.versions]]
 version = "v0.13"
 url = "https://haproxy-ingress.github.io/v0.13/docs"
@@ -95,18 +99,10 @@ url = "https://haproxy-ingress.github.io/v0.13/docs"
 version = "v0.12"
 url = "https://haproxy-ingress.github.io/v0.12/docs"
 
-[[params.versions]]
-version = "v0.11"
-url = "https://haproxy-ingress.github.io/v0.11/docs"
-
 [[params.versions]]
 version = "v0.10"
 url = "https://haproxy-ingress.github.io/v0.10/docs"
 
-[[params.versions]]
-version = "v0.9"
-url = "https://haproxy-ingress.github.io/v0.9/docs"
-
 # User interface configuration
 [params.ui]
 # Enable to show the side bar menu in its compact state.

docs/content/en/docs/getting-started/_index.md

@@ -10,7 +10,7 @@ The following sections walk through steps to have HAProxy Ingress working, watch
 
 ## Prerequisites
 
-HAProxy Ingress needs a running Kubernetes cluster. Controller version v0.13 needs Kubernetes 1.19 or newer, see other supported versions in the [README](https://github.com/jcmoraisjr/haproxy-ingress/#use-haproxy-ingress) file. HAProxy Ingress also works fine on local k8s deployments like [minikube](https://minikube.sigs.k8s.io), [kind](https://kind.sigs.k8s.io) or [k3d](https://k3d.io).
+HAProxy Ingress needs a running Kubernetes cluster. Controller version v0.14 needs Kubernetes 1.19 or newer, see other supported versions in the [README](https://github.com/jcmoraisjr/haproxy-ingress/#use-haproxy-ingress) file. HAProxy Ingress also works fine on local k8s deployments like [minikube](https://minikube.sigs.k8s.io), [kind](https://kind.sigs.k8s.io) or [k3d](https://k3d.io).
 
 An ingress controller works exposing internal services to the external world, so another pre-requisite is that at least one cluster node is accessible externally. On cloud environments, a cloud load balancer can be configured to reach the ingress controller nodes.
 
@@ -45,14 +45,14 @@ controller:
   hostNetwork: true
 ```
 
-HAProxy Ingress chart [documentation](https://github.com/haproxy-ingress/charts/blob/release-0.13/haproxy-ingress/README.md#configuration) has all the available options. See also further documentation in the [default values](https://github.com/haproxy-ingress/charts/blob/release-0.13/haproxy-ingress/values.yaml) file.
+HAProxy Ingress chart [documentation](https://github.com/haproxy-ingress/charts/blob/release-0.14/haproxy-ingress/README.md#configuration) has all the available options. See also further documentation in the [default values](https://github.com/haproxy-ingress/charts/blob/release-0.14/haproxy-ingress/values.yaml) file.
 
 5) Install HAProxy Ingress using `haproxy-ingress` as the release name and `haproxy-ingress-values.yaml` file as the custom parameters:
 
 ```shell
 $ helm install haproxy-ingress haproxy-ingress/haproxy-ingress\
   --create-namespace --namespace ingress-controller\
-  --version 0.13.0-beta.1 --devel\
+  --version 0.14.0-alpha.1 --devel\
   -f haproxy-ingress-values.yaml
 ```
 
@@ -66,7 +66,7 @@ The controller should be running in a few seconds. There are three important cus
 * namespace: we're instructing helm to install HAProxy Ingress in the `ingress-controller` namespace. This namespace will be created if it does not exist yet. The default behavior, if namespace is not provided, is to deploy the controller in the kubectl's current namespace.
 * hostNetwork: we're configuring the deployment to expose haproxy in the host network, which means bind all haproxy ports, including but not limited to 80 and 443, in the node's IPs. Maybe this isn't a proper configuration for your production - it depends on the options you have to expose a Kubernetes' service, but doing so we'll be able to send http/s requests on local development environments, or even baremetal and on premise deployments that doesn't have a fronting router or load balancer to expose the controller. In any case a service is also configured in the `ingress-controller` namespace which tries to expose haproxy.
 
-HAProxy Ingress' Helm chart has a few more configuration options, see all of them in the chart [documentation](https://github.com/haproxy-ingress/charts/blob/release-0.13/haproxy-ingress/README.md) and in the [default values](https://github.com/haproxy-ingress/charts/blob/release-0.13/haproxy-ingress/values.yaml) file.
+HAProxy Ingress' Helm chart has a few more configuration options, see all of them in the chart [documentation](https://github.com/haproxy-ingress/charts/blob/release-0.14/haproxy-ingress/README.md) and in the [default values](https://github.com/haproxy-ingress/charts/blob/release-0.14/haproxy-ingress/values.yaml) file.
 
 ## Deploy and expose