You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployments/helm-chart/README.md
+30-7Lines changed: 30 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,14 +8,36 @@ This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
8
8
9
9
- Kubernetes 1.6+.
10
10
- Helm 2.8.x+.
11
-
- Git.
11
+
- Git (for installation using the chart source files).
12
12
- If you’d like to use NGINX Plus:
13
-
- Build an Ingress controller image with NGINX Plus and push it to your private registry by following the instructions from [here](../../build/README.md).
14
-
-Update the `controller.image.repository`field of the `values-plus.yaml` accordingly.
13
+
- Build an Ingress controller image with NGINX Plus and push it to your private registry by following the instructions from [here](https://github.com/nginxinc/kubernetes-ingress/blob/v1.4.3/build/README.md).
14
+
-Configure `controller.nginxplus` and `controller.image.repository`parameters accordingly using a values file or the `--set` flag of the `helm install` command.
@@ -31,14 +53,15 @@ This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
31
53
$ helm install --name my-release .
32
54
```
33
55
34
-
For NGINX Plus:
56
+
For NGINX Plus (assuming you have configured the `controller.nginxplus` and `controller.image.repository` parameters in the values file `values-plus.yaml`):
The command deploys the Ingress controller in your Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
61
+
### Notes
40
62
41
-
When deploying the Ingress controller, make sure to use your own TLS certificate and key for the default server rather than the default pre-generated ones. Read the [Configuration](#Configuration) section below to see how to configure a TLS certificate and key for the default server. Note that the default server returns the Not Found page with the 404 status code for all requests for domains for which there are no Ingress rules defined.
63
+
* The `helm install` command deploys the Ingress controller in your Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.
64
+
* When deploying the Ingress controller, make sure to use your own TLS certificate and key for the default server rather than the default pre-generated ones. Read the [Configuration](#Configuration) section below to see how to configure a TLS certificate and key for the default server. Note that the default server returns the Not Found page with the 404 status code for all requests for domains for which there are no Ingress rules defined.
0 commit comments