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: helm-chart/README.md
+50-30Lines changed: 50 additions & 30 deletions
Original file line number
Diff line number
Diff line change
@@ -2,36 +2,48 @@
2
2
3
3
## Introduction
4
4
5
-
This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
5
+
This chart deploys the NGINX Ingress controller in your Kubernetes cluster.
6
6
7
7
## Prerequisites
8
8
9
9
- Kubernetes 1.6+.
10
-
- If you’d like to use NGINX Plus, you need to build your own Docker image and push it to your private registry by following the instructions from [here](../nginx-controller/README.md).
10
+
- Helm 2.8.x+.
11
+
- Git.
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](../nginx-controller/README.md).
14
+
- Update the `controller.image.repository` field of the `values-plus.yaml` accordingly.
11
15
12
16
## Installing the Chart
13
17
14
-
To install the chart with the release name my-release:
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.
38
+
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.
29
39
30
-
> **Tip**: List all releases using helm list
40
+
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.
`controller.name` | The name of the Ingress controller daemon set or deployment. | nginx-ingress
49
61
`controller.kind` | The kind of the Ingress controller installation - deployment or daemonset. | deployment
50
-
`controller.nginxplus` | Should NGINX Plus be deployed. | false
51
-
`controller.hostNetwork` | If the nginx deployment / daemonset should run on the host's network namespace. | false
62
+
`controller.nginxplus` | Deploys the Ingress controller for NGINX Plus. | false
63
+
`controller.hostNetwork` | Enables the Ingress controller pods to use the host's network namespace. | false
52
64
`controller.image.repository` | The image repository of the Ingress controller. | nginx/nginx-ingress
53
65
`controller.image.tag` | The tag of the Ingress controller image. | 1.2.0
54
66
`controller.image.pullPolicy` | The pull policy for the Ingress controller image. | IfNotPresent
55
67
`controller.config.entries` | The entries of the ConfigMap for customizing NGINX configuration. | { }
56
-
`controller.defaultTLS.cert` | The TLS certificate for the default HTTPS server. | None
57
-
`controller.defaultTLS.key` | The TLS key for the default HTTPS server. | None
58
-
`controller.nodeselector` | The node selectorlabels for pod assignment for the Ingress controller pods. | { }
68
+
`controller.defaultTLS.cert` | The base64-encoded TLS certificate for the default HTTPS server. If not specified, a pre-generated self-signed certificate is used. **Note:** It is recommended that you specify your own certificate. | A pre-generated self-signed certificate.
69
+
`controller.defaultTLS.key` | The base64-encoded TLS key for the default HTTPS server. **Note:** If not specified, a pre-generated key is used. It is recommended that you specify your own key. | A pre-generated key.
70
+
`controller.defaultTLS.secret` | The secret with a TLS certificate and key for the default HTTPS server. The value must follow the following format: `<namespace>/<name>`. Used as an alternative to specifiying a certifcate and key using `controller.defaultTLS.cert` and `controller.defaultTLS.key` parameters. | None
71
+
`controller.nodeSelector` | The node selector for pod assignment for the Ingress controller pods. | { }
59
72
`controller.terminationGracePeriodSeconds` | The termination grace period of the Ingress controller pod. | 30
60
-
`controller.tolerations` | The tolerations required for the IBM Cloud Platform installation. | None
61
-
62
-
63
-
64
-
## Limitations
65
-
66
-
This is a preview version of our helm chart. It has limitations including support for cloud installations (except for the IBM Cloud Platform) and RBAC. This version is not suitable for using in production environments.
67
-
68
-
73
+
`controller.tolerations` | The tolerations required for the IBM Cloud Private installation. | None
74
+
`controller.replicaCount` | The number of replicas of the Ingress controller deployment. | 1
75
+
`controller.service.create` | Creates a service to expose the Ingress controller pods. | true
76
+
`controller.service.type` | The type of service to create for the Ingress controller. | LoadBalancer
77
+
`controller.service.externalTrafficPolicy` | The externalTrafficPolicy of the service. The value Local preserves the client source IP. | Local
78
+
`controller.service.annotations` | The annotations of the Ingress controller service. | {}
79
+
`controller.serviceAccountName` | The serviceAccountName of the Ingress controller pods. Used for RBAC. | nginx-ingress
* The values-icp.yaml file is used for deploying the Ingress controller on IBM Cloud Private. See the [blog post](https://www.nginx.com/blog/nginx-ingress-controller-ibm-cloud-private/) for more details.
0 commit comments