Skip to content

Commit

Permalink
Release 1.9.1
Browse files Browse the repository at this point in the history
  • Loading branch information
Dean-Coakley committed Nov 23, 2020
1 parent 9f1c285 commit aa19bb4
Show file tree
Hide file tree
Showing 31 changed files with 107 additions and 73 deletions.
16 changes: 16 additions & 0 deletions CHANGELOG.md
@@ -1,5 +1,21 @@
# Changelog

### 1.9.1

CHANGES:
* Fix deployment of ingressclass resource via helm on some versions of Kubernetes.
* Update the base ubi images to 8.3.
* Renew CA cert for egress-mtls example.
* Add `controller.serviceAccount.imagePullSecretName` parameter to the helm chart. **Note**: `controller.serviceAccount.imagePullSecrets` is deprecated and will be removed in the future `1.10.0` release.

HELM CHART:
* The version of the Helm chart is now 0.7.1.

UPGRADE:
* For NGINX, use the 1.9.1 image from our DockerHub: `nginx/nginx-ingress:1.9.1`, `nginx/nginx-ingress:1.9.1-alpine` or `nginx/nginx-ingress:1.9.1-ubi`
* For NGINX Plus, please build your own image using the 1.9.1 source code.
* For Helm, use version 0.7.1 of the chart.

### 1.9.0

OVERVIEW:
Expand Down
2 changes: 1 addition & 1 deletion Makefile
@@ -1,6 +1,6 @@
all: push

VERSION = 1.9.0
VERSION = 1.9.1
TAG = $(VERSION)
PREFIX = nginx/nginx-ingress

Expand Down
4 changes: 2 additions & 2 deletions README.md
Expand Up @@ -53,7 +53,7 @@ Read [this doc](docs/nginx-plus.md) to learn more about NGINX Ingress controller

We publish Ingress controller releases on GitHub. See our [releases page](https://github.com/nginxinc/kubernetes-ingress/releases).

The latest stable release is [1.9.0](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.9.0). For production use, we recommend that you choose the latest stable release. As an alternative, you can choose the *edge* version built from the [latest commit](https://github.com/nginxinc/kubernetes-ingress/commits/master) from the master branch. The edge version is useful for experimenting with new features that are not yet published in a stable release.
The latest stable release is [1.9.1](https://github.com/nginxinc/kubernetes-ingress/releases/tag/v1.9.1). For production use, we recommend that you choose the latest stable release. As an alternative, you can choose the *edge* version built from the [latest commit](https://github.com/nginxinc/kubernetes-ingress/commits/master) from the master branch. The edge version is useful for experimenting with new features that are not yet published in a stable release.

To use the Ingress controller, you need to have access to:
* An Ingress controller image.
Expand All @@ -66,7 +66,7 @@ The table below summarizes the options regarding the images, manifests, helm cha

| Version | Description | Image for NGINX | Image for NGINX Plus | Installation Manifests and Helm Chart | Documentation and Examples |
| ------- | ----------- | --------------- | -------------------- | ---------------------------------------| -------------------------- |
| Latest stable release | For production use | `nginx/nginx-ingress:1.9.0`, `nginx/nginx-ingress:1.9.0-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). | [Build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/deployments/helm-chart). | [Documentation](https://docs.nginx.com/nginx-ingress-controller/). [Examples](https://docs.nginx.com/nginx-ingress-controller/configuration/configuration-examples/). |
| Latest stable release | For production use | `nginx/nginx-ingress:1.9.1`, `nginx/nginx-ingress:1.9.1-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). | [Build your own image](https://docs.nginx.com/nginx-ingress-controller/installation/building-ingress-controller-image/). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/deployments/helm-chart). | [Documentation](https://docs.nginx.com/nginx-ingress-controller/). [Examples](https://docs.nginx.com/nginx-ingress-controller/configuration/configuration-examples/). |
| Edge | For testing and experimenting | `nginx/nginx-ingress:edge`, `nginx/nginx-ingress:edge-alpine` from [DockerHub](https://hub.docker.com/r/nginx/nginx-ingress/) or [build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/master/docs-web/installation/building-ingress-controller-image.md). | [Build your own image](https://github.com/nginxinc/kubernetes-ingress/tree/master/docs-web/installation/building-ingress-controller-image.md). | [Manifests](https://github.com/nginxinc/kubernetes-ingress/tree/master/deployments). [Helm chart](https://github.com/nginxinc/kubernetes-ingress/tree/master/deployments/helm-chart). | [Documentation](https://github.com/nginxinc/kubernetes-ingress/tree/master/docs-web). [Examples](https://github.com/nginxinc/kubernetes-ingress/tree/master/examples). |

## Contacts
Expand Down
2 changes: 1 addition & 1 deletion deployments/daemon-set/nginx-ingress.yaml
Expand Up @@ -17,7 +17,7 @@ spec:
spec:
serviceAccountName: nginx-ingress
containers:
- image: nginx/nginx-ingress:1.9.0
- image: nginx/nginx-ingress:1.9.1
imagePullPolicy: IfNotPresent
name: nginx-ingress
ports:
Expand Down
2 changes: 1 addition & 1 deletion deployments/daemon-set/nginx-plus-ingress.yaml
Expand Up @@ -17,7 +17,7 @@ spec:
spec:
serviceAccountName: nginx-ingress
containers:
- image: nginx-plus-ingress:1.9.0
- image: nginx-plus-ingress:1.9.1
imagePullPolicy: IfNotPresent
name: nginx-plus-ingress
ports:
Expand Down
2 changes: 1 addition & 1 deletion deployments/deployment/nginx-ingress.yaml
Expand Up @@ -18,7 +18,7 @@ spec:
spec:
serviceAccountName: nginx-ingress
containers:
- image: nginx/nginx-ingress:1.9.0
- image: nginx/nginx-ingress:1.9.1
imagePullPolicy: IfNotPresent
name: nginx-ingress
ports:
Expand Down
2 changes: 1 addition & 1 deletion deployments/deployment/nginx-plus-ingress.yaml
Expand Up @@ -18,7 +18,7 @@ spec:
spec:
serviceAccountName: nginx-ingress
containers:
- image: nginx-plus-ingress:1.9.0
- image: nginx-plus-ingress:1.9.1
imagePullPolicy: IfNotPresent
name: nginx-plus-ingress
ports:
Expand Down
8 changes: 4 additions & 4 deletions deployments/helm-chart/Chart.yaml
@@ -1,12 +1,12 @@
name: nginx-ingress
version: 0.7.0
appVersion: 1.9.0
version: 0.7.1
appVersion: 1.9.1
apiVersion: v1
kubeVersion: ">= 1.14.0-0"
description: NGINX Ingress Controller
icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v1.9.0/deployments/helm-chart/chart-icon.png
icon: https://raw.githubusercontent.com/nginxinc/kubernetes-ingress/v1.9.1/deployments/helm-chart/chart-icon.png
sources:
- https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/deployments/helm-chart
- https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/deployments/helm-chart
keywords:
- ingress
- nginx
Expand Down
4 changes: 2 additions & 2 deletions deployments/helm-chart/README.md
Expand Up @@ -24,7 +24,7 @@ This step is required if you're installing the chart using its sources. Addition
2. Change your working directory to /deployments/helm-chart:
```console
$ cd kubernetes-ingress/deployments/helm-chart
$ git checkout v1.9.0
$ git checkout v1.9.1
```

## Adding the Helm Repository
Expand Down Expand Up @@ -195,7 +195,7 @@ Parameter | Description | Default
`controller.nginxDebug` | Enables debugging for NGINX. Uses the `nginx-debug` binary. Requires `error-log-level: debug` in the ConfigMap via `controller.config.entries`. | false
`controller.logLevel` | The log level of the Ingress Controller. | 1
`controller.image.repository` | The image repository of the Ingress controller. | nginx/nginx-ingress
`controller.image.tag` | The tag of the Ingress controller image. | 1.9.0
`controller.image.tag` | The tag of the Ingress controller image. | 1.9.1
`controller.image.pullPolicy` | The pull policy for the Ingress controller image. | IfNotPresent
`controller.config.name` | The name of the ConfigMap used by the Ingress controller. | Autogenerated
`controller.config.annotations` | The annotations of the Ingress controller configmap. | {}
Expand Down
2 changes: 1 addition & 1 deletion deployments/helm-chart/values-icp.yaml
Expand Up @@ -3,7 +3,7 @@ controller:
nginxplus: true
image:
repository: mycluster.icp:8500/kube-system/nginx-plus-ingress
tag: "1.9.0"
tag: "1.9.1"
nodeSelector:
beta.kubernetes.io/arch: "amd64"
proxy: true
Expand Down
2 changes: 1 addition & 1 deletion deployments/helm-chart/values-plus.yaml
Expand Up @@ -2,4 +2,4 @@ controller:
nginxplus: true
image:
repository: nginx-plus-ingress
tag: "1.9.0"
tag: "1.9.1"
2 changes: 1 addition & 1 deletion deployments/helm-chart/values.yaml
Expand Up @@ -36,7 +36,7 @@ controller:
repository: nginx/nginx-ingress

## The tag of the Ingress controller image.
tag: "1.9.0"
tag: "1.9.1"

## The pull policy for the Ingress controller image.
pullPolicy: IfNotPresent
Expand Down
4 changes: 2 additions & 2 deletions docs-web/app-protect/configuration.md
@@ -1,12 +1,12 @@
# Configuration
This document describes how to configure the NGINX App Protect module
> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/appprotect).
> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/appprotect).
## Global Configuration

The NGINX Ingress Controller has a set of global configuration parameters that align with those available in the NGINX App Protect module. See [ConfigMap keys](/nginx-ingress-controller/configuration/global-configuration/configmap-resource/#modules) for the complete list. The App Protect parameters use the `app-protect*` prefix.

> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/appprotect).
> Check out the complete [NGINX Ingress Controller with App Protect example resources on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/appprotect).
## Enable App Protect for an Ingress Resource

Expand Down
2 changes: 1 addition & 1 deletion docs-web/app-protect/installation.md
Expand Up @@ -36,5 +36,5 @@ Take the steps below to set up and deploy the NGINX Ingress Controller and App P
3. Enable the App Protect module by adding the `enable-app-protect` [cli argument](/nginx-ingress-controller/configuration/global-configuration/command-line-arguments/#cmdoption-enable-app-protect) to your Deployment or DaemonSet file.
4. [Deploy the Ingress Controller](/nginx-ingress-controller/installation/installation-with-manifests/#deploy-the-ingress-controller).

For more information, see the [Configuration guide](/nginx-ingress-controller/app-protect/configuration) and the [NGINX Ingress Controller with App Protect examples on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/appprotect).
For more information, see the [Configuration guide](/nginx-ingress-controller/app-protect/configuration) and the [NGINX Ingress Controller with App Protect examples on GitHub](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/appprotect).

4 changes: 2 additions & 2 deletions docs-web/configuration/configuration-examples.md
@@ -1,5 +1,5 @@
# Configuration Examples

Our [GitHub repo](https://github.com/nginxinc/kubernetes-ingress) includes a number of configuration examples:
* [*Examples*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples) show how to use advanced NGINX features in Ingress resources with annotations.
* [*Examples of Custom Resources*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples-of-custom-resources) show how to use VirtualServer and VirtualServerResources for a few use cases.
* [*Examples*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples) show how to use advanced NGINX features in Ingress resources with annotations.
* [*Examples of Custom Resources*](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples-of-custom-resources) show how to use VirtualServer and VirtualServerResources for a few use cases.
22 changes: 11 additions & 11 deletions docs-web/configuration/global-configuration/configmap-resource.md
Expand Up @@ -149,19 +149,19 @@ See the doc about [VirtualServer and VirtualServerRoute resources](/nginx-ingres
* - ``resolver-addresses``
- Sets the value of the `resolver <https://nginx.org/en/docs/http/ngx_http_core_module.html#resolver>`_ addresses. Note: If you use a DNS name (ex., ``kube-dns.kube-system.svc.cluster.local``\ ) as a resolver address, NGINX Plus will resolve it using the system resolver during the start and on every configuration reload. As a consequence, If the name cannot be resolved or the DNS server doesn't respond, NGINX Plus will fail to start or reload. To avoid this, consider using only IP addresses as resolver addresses. Supported in NGINX Plus only.
- N/A
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/externalname-services>`_.
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/externalname-services>`_.
* - ``resolver-ipv6``
- Enables IPv6 resolution in the resolver. Supported in NGINX Plus only.
- ``True``
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/externalname-services>`_.
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/externalname-services>`_.
* - ``resolver-valid``
- Sets the time NGINX caches the resolved DNS records. Supported in NGINX Plus only.
- TTL value of a DNS record
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/externalname-services>`_.
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/externalname-services>`_.
* - ``resolver-timeout``
- Sets the `resolver_timeout <https://nginx.org/en/docs/http/ngx_http_core_module.html#resolver_timeout>`_ for name resolution. Supported in NGINX Plus only.
- ``30s``
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/externalname-services>`_.
- `Support for Type ExternalName Services <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/externalname-services>`_.
* - ``keepalive-timeout``
- Sets the value of the `keepalive_timeout <https://nginx.org/en/docs/http/ngx_http_core_module.html#keepalive_timeout>`_ directive.
- ``65s``
Expand Down Expand Up @@ -204,15 +204,15 @@ See the doc about [VirtualServer and VirtualServerRoute resources](/nginx-ingres
-
* - ``log-format``
- Sets the custom `log format <https://nginx.org/en/docs/http/ngx_http_log_module.html#log_format>`_ for HTTP and HTTPS traffic. For convenience, it is possible to define the log format across multiple lines (each line separated by ``\n``). In that case, the Ingress Controller will replace every ``\n`` character with a space character. All ``'`` characters must be escaped.
- See the `template file <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.0/internal/configs/version1/nginx.tmpl>`_ for the access log.
- See the `template file <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.1/internal/configs/version1/nginx.tmpl>`_ for the access log.
-
* - ``log-format-escaping``
- Sets the characters escaping for the variables of the log format. Supported values: ``json`` (JSON escaping), ``default`` (the default escaping) ``none`` (disables escaping).
- ``default``
-
* - ``stream-log-format``
- Sets the custom `log format <https://nginx.org/en/docs/stream/ngx_stream_log_module.html#log_format>`_ for TCP, UDP, and TLS Passthrough traffic. For convenience, it is possible to define the log format across multiple lines (each line separated by ``\n``). In that case, the Ingress Controller will replace every ``\n`` character with a space character. All ``'`` characters must be escaped.
- See the `template file <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.0/internal/configs/version1/nginx.tmpl>`_.
- See the `template file <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.1/internal/configs/version1/nginx.tmpl>`_.
-
* - ``stream-log-format-escaping``
- Sets the characters escaping for the variables of the stream log format. Supported values: ``json`` (JSON escaping), ``default`` (the default escaping) ``none`` (disables escaping).
Expand Down Expand Up @@ -309,7 +309,7 @@ See the doc about [VirtualServer and VirtualServerRoute resources](/nginx-ingres
* - ``proxy-protocol``
- Enables PROXY Protocol for incoming connections.
- ``False``
- `Proxy Protocol <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/proxy-protocol>`_.
- `Proxy Protocol <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/proxy-protocol>`_.
```

### Backend Services (Upstreams)
Expand Down Expand Up @@ -373,7 +373,7 @@ See the doc about [VirtualServer and VirtualServerRoute resources](/nginx-ingres
* - ``stream-snippets``
- Sets a custom snippet in stream context.
- N/A
- `Support for TCP/UDP Load Balancing <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/tcp-udp>`_.
- `Support for TCP/UDP Load Balancing <https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/tcp-udp>`_.
* - ``main-template``
- Sets the main NGINX configuration template.
- By default the template is read from the file in the container.
Expand Down Expand Up @@ -401,15 +401,15 @@ See the doc about [VirtualServer and VirtualServerRoute resources](/nginx-ingres
* - ``opentracing``
- Enables `OpenTracing <https://opentracing.io>`_ globally (for all Ingress, VirtualServer and VirtualServerRoute resources). Note: requires the Ingress Controller image with OpenTracing module and a tracer. See the `docs </nginx-ingress-controller/third-party-modules/opentracing>`_ for more information.
- ``False``
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.0/examples/opentracing/README.md>`_.
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.1/examples/opentracing/README.md>`_.
* - ``opentracing-tracer``
- Sets the path to the vendor tracer binary plugin.
- N/A
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.0/examples/opentracing/README.md>`_.
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.1/examples/opentracing/README.md>`_.
* - ``opentracing-tracer-config``
- Sets the tracer configuration in JSON format.
- N/A
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.0/examples/opentracing/README.md>`_.
- `Support for OpenTracing <https://github.com/nginxinc/kubernetes-ingress/blob/v1.9.1/examples/opentracing/README.md>`_.
* - ``app-protect-cookie-seed``
- Sets the ``app_protect_cookie_seed`` `global directive </nginx-app-protect/configuration/#global-directives>`_.
- Random automatically generated string
Expand Down
@@ -1,3 +1,3 @@
# Custom Templates

The Ingress Controller uses templates to generate NGINX configuration for Ingress resources, VirtualServer resources and the main NGINX configuration file. You can customize the templates and apply them via the ConfigMap. See the [corresponding example](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.0/examples/custom-templates).
The Ingress Controller uses templates to generate NGINX configuration for Ingress resources, VirtualServer resources and the main NGINX configuration file. You can customize the templates and apply them via the ConfigMap. See the [corresponding example](https://github.com/nginxinc/kubernetes-ingress/tree/v1.9.1/examples/custom-templates).

0 comments on commit aa19bb4

Please sign in to comment.