NGINX and NGINX Plus Ingress Controllers for Kubernetes
APACHE-2.0 License
Bot releases are hidden (Show)
Published by lucacome over 2 years ago
Published by lucacome about 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
nginx/nginx-ingress:2.0.2
, nginx/nginx-ingress:2.0.2-alpine
, nginx/nginx-ingress:2.0.2-ubi
or nginx/nginx-ingress:2.0.2-ot
Published by lucacome about 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
nginx/nginx-ingress:2.0.1
, nginx/nginx-ingress:2.0.1-alpine
, nginx/nginx-ingress:2.0.1-ubi
or nginx/nginx-ingress:2.0.1-ot
Published by lucacome about 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
nginx/nginx-ingress:1.12.2
, nginx/nginx-ingress:1.12.2-alpine
or nginx/nginx-ingress:1.12.2-ubi
Published by ciarams87 about 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
nginx/nginx-ingress:1.12.1
, nginx/nginx-ingress:1.12.1-alpine
or nginx/nginx-ingress:1.12.1-ubi
Published by pleshakov over 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
Published by ciarams87 over 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
Published by ciarams87 over 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
nginx/nginx-ingress:1.11.1
, nginx/nginx-ingress:1.11.1-alpine
or nginx/nginx-ingress:1.11.1-ubi
Published by lucacome over 3 years ago
Help make the NGINX Ingress Controller better by participating in our survey!
Fix various issues in the Makefile. In 1.10.0, a bug was introduced that prevented building Ingress Controller images on versions of make < 4.1. (#1373) (#1439) (#1440)
nginx/nginx-ingress:1.10.1
, nginx/nginx-ingress:1.10.1-alpine
or nginx/nginx-ingress:1.10.1-ubi
Published by Dean-Coakley over 3 years ago
OVERVIEW:
Release 1.10.0 includes:
You will find the complete changelog for release 1.10.0, including bug fixes, improvements, and changes below.
FEATURES FOR POLICY RESOURCE:
FEATURES FOR NGINX APP PROTECT:
FEATURES:
IMPROVEMENTS:
HELM CHART:
controller.enablePreviewPolicies
was added.controller.serviceAccount.imagePullSecrets
was removed. controller.serviceAccount.imagePullSecretName
was added.v1.18.x-*
CHANGES:
debian:buster-slim
.1.19.6
. Update NGINX Plus to R23
.UPGRADE:
For NGINX, use the 1.10.0 image from our DockerHub: nginx/nginx-ingress:1.10.0
, nginx/nginx-ingress:1.10.0-alpine
or nginx-ingress:1.10.0-ubi
For NGINX Plus, please build your own image using the 1.10.0 source code.
For Helm, use version 0.8.0 of the chart.
As a result of 1270 and 1277, the Ingress Controller improved validation of Ingress annotations: more annotations are validated and validation errors are reported via events for Ingress resources. Additionally, the default behavior for invalid annotation values was changed: instead of using the default values, the Ingress Controller will reject a resource with an invalid annotation value, which will make clients see 404
responses from NGINX. See this document to learn more. Before upgrading, ensure the Ingress resources don't have annotations with invalid values. Otherwise, after the upgrade, the Ingress Controller will reject such resources.
In 1232 controller.serviceAccount.imagePullSecrets
was removed. Use the new controller.serviceAccount.imagePullSecretName
instead.
The Policy resource was promoted to v1
. If you used the alpha1
version, the policies are needed to be recreated with the v1
version. Before upgrading the Ingress Controller, run the following command to remove the alpha1
policies CRD (that will also remove all existing alpha1
policies):
kubectl delete crd policies.k8s.nginx.org
As part of the upgrade, make sure to create the v1
policies CRD. See the corresponding instructions for the manifests and Helm installations.
Also note that all policies except for accessControl
are still in preview. To enable them, run the Ingress Controller with - -enable-preview-policies
command-line argument (controller.enablePreviewPolicies
Helm parameter).
It is necessary to update secret resources. See the section UPDATING SECRETS below.
UPDATING SECRETS:
In 1225, as part of improving how the Ingress Controller handles secret resources, we added a requirement for secrets to be of one of the following types:
kubernetes.io/tls
for TLS secrets.nginx.org/jwk
for JWK secrets.nginx.org/ca
for CA secrets.The Ingress Controller now ignores secrets that are not of a supported type. As a consequence, special upgrade steps are required.
Before upgrading, ensure that the secrets referenced in Ingress, VirtualServer or Policies resources are of a supported type, which is configured via the type
field. Because that field is immutable, it is necessary to either:
It is also necessary to update the default server secret and the wildcard secret (if it was configured) in case their type is not kubernetes.io/tls
. The steps depend on how you installed the Ingress Controller: via manifests or Helm. Performing the steps will not lead to a disruption of the client traffic, as the Ingress Controller retains the default and wildcard secrets if they are removed.
For manifests installation:
kubernetes.io/tls
.For Helm installation, there two cases:
controller.defaultTLS.cert
and controller.defaultTLS.key
for the default secret and controller.wildcardTLS.cert
and controller.wildcardTLS.key
for the wildcard secret), then no special upgrade steps are required: during the upgrade, the Helm will remove the existing default and wildcard secrets and create new ones with different names with the type kubernetes.io/tls
.controller.defaultTLS.secret
for the default secret and controller.wildcardTLS.secret
for the wildcard secret):
kubernetes.io/tls
.NOTES:
RESOURCES:
Published by Dean-Coakley almost 4 years ago
CHANGES:
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:
UPGRADE:
nginx/nginx-ingress:1.9.1
, nginx/nginx-ingress:1.9.1-alpine
or nginx/nginx-ingress:1.9.1-ubi
RESOURCES:
Published by Dean-Coakley almost 4 years ago
OVERVIEW:
Release 1.9.0 includes:
You will find the complete changelog for release 1.9.0, including bug fixes, improvements, and changes below.
FEATURES FOR POLICY RESOURCE:
FEATURES FOR NGINX APP PROTECT:
FEATURES:
IMPROVEMENTS:
BUGFIXES:
HELM CHART:
controller.setAsDefaultIngress
, controller.enableLatencyMetrics
. Added in 1133 and 1148.CHANGES:
UPGRADE:
nginx/nginx-ingress:1.9.0
, nginx/nginx-ingress:1.9.0-alpine
or nginx-ingress:1.9.0-ubi
For Kubernetes >= 1.18, when upgrading using the manifests, make sure to update the ClusterRole and create the IngressClass resource, which is required for Kubernetes >= 1.18. Otherwise, the Ingress Controller will fail to start. If you run multiple NGINX Ingress Controllers in the cluster, each Ingress Controller has to have its own IngressClass resource. As the -use-ingress-class-only
argument is now ignored (see NOTES), make sure your Ingress resources have the ingressClassName
field or the kubernetes.io/ingress.class
annotation set to the name of the IngressClass resource. Otherwise, the Ingress Controller will ignore them.
HELM UPGRADE:
controller.enableCustomResources
is set to true
), after you run the helm upgrade
command, the CRDs will not be upgraded. After running the helm upgrade
command, run kubectl apply -f deployments/helm-chart/crds
to upgrade the CRDs.controller.ingressClass
, is required per helm release. Ensure controller.ingressClass
is not set to the name of the IngressClass of other releases or Ingress Controllers. As the controller.useIngressClassOnly
parameter is now ignored (see NOTES), make sure your Ingress resources have the ingressClassName
field or the kubernetes.io/ingress.class
annotation set to the value of controller.ingressClass
. Otherwise, the Ingress Controller will ignore them.NOTES:
-use-ingress-class-only
command-line argument is now ignored, and the Ingress Controller will only process resources that belong to its class. See IngressClass doc to learn more.controller.ingressClass
, is required per helm release. When upgrading or installing releases, ensure controller.ingressClass
is not set to the name of the IngressClass of other releases or Ingress Controllers.RESOURCES:
Published by LorcanMcVeigh about 4 years ago
CHANGES:
HELM CHART:
UPGRADE:
nginx/nginx-ingress:1.8.1
, nginx/nginx-ingress:1.8.1-alpine
or nginx/nginx-ingress:1.8.1-ubi
KNOWN ISSUES:
controller.globalConfiguration.create
set to true
. A workaround is described here.RESOURCES:
Published by Rulox about 4 years ago
OVERVIEW:
Release 1.8.0 includes:
You will find the complete changelog for release 1.8.0, including bug fixes, improvements, and changes below.
FEATURES FOR VIRTUALSERVER AND VIRTUALSERVERROUTE RESOURCES:
FEATURES:
IMPROVEMENTS:
BUGFIXES:
HELM CHART:
controller.appprotect.enable
, controller.globalConfiguration.create
, controller.globalConfiguration.spec
, controller.readyStatus.enable
, controller.readyStatus.port
, controller.config.annotations
, controller.reportIngressStatus.annotations
. Added in 1035, 1034, 1029, 1003 thanks to RubyLangdon.controller.enableCustomResources
is set to true
), this is a breaking change. See the HELM UPGRADE section below for the upgrade instructions.CHANGES:
8081
and the path /nginx-ready
. The endpoint returns a 200
response after the Ingress Controller finishes the initial configuration of NGINX at the start. The pod template was updated to use that endpoint in a readiness probe.UPGRADE:
nginx/nginx-ingress:1.8.0
, nginx/nginx-ingress:1.8.0-alpine
or nginx-ingress:1.8.0-ubi
HELM UPGRADE:
If you're using custom resources like VirtualServer and TransportServer (controller.enableCustomResources
is set to true
), after you run the helm upgrade
command, the CRDs and the corresponding custom resources will be removed from the cluster. Before upgrading, make sure to back up the custom resources. After running the helm upgrade
command, run kubectl apply -f deployments/helm-chart/crds
to re-install the CRDs and then restore the custom resources.
NOTES:
aplogconfs.appprotect.f5.com
and appolicies.appprotect.f5.com
CRDs).RESOURCES:
Published by LorcanMcVeigh over 4 years ago
CHANGES:
HELM CHART:
UPGRADE:
nginx/nginx-ingress:1.7.2
, nginx/nginx-ingress:1.7.2-alpine
or nginx/nginx-ingress:1.7.2-ubi
RESOURCES:
NOTES:
After the release, the tag v1.7.2
was updated to point to a new commit. This was done to fix a problem with the release - the version of NGINX Plus wasn't updated to R22
in the Dockerfiles. If you checked out the source code with the old version of the v1.7.2
tag, make sure to run the following command to update v1.7.2
on your machine:
$ git tag -d v1.7.2
$ git fetch origin tag v1.7.2
Published by LorcanMcVeigh over 4 years ago
CHANGES:
HELM CHART:
UPGRADE:
nginx/nginx-ingress:1.7.1
, nginx/nginx-ingress:1.7.1-alpine
or nginx/nginx-ingress:1.7.1-ubi
RESOURCES:
Published by pleshakov over 4 years ago
OVERVIEW:
Release 1.7.0 includes:
See the 1.7.0 release announcement blog post, which includes an overview of each feature.
You will find the complete changelog for release 1.7.0, including bug fixes, improvements, and changes at https://github.com/nginxinc/kubernetes-ingress/blob/v1.7.0/CHANGELOG.md#170
UPGRADE:
nginx/nginx-ingress:1.7.0
, nginx/nginx-ingress:1.7.0-alpine
or nginx-ingress:1.7.0-ubi
When upgrading using the manifests, make sure to deploy the new TransportServer CRD (common/ts-definition.yaml
), as it is required by the Ingress Controller. Otherwise, you will get error messages in the Ingress Controller logs.
RESOURCES:
Published by pleshakov over 4 years ago
OVERVIEW:
Release 1.7.0-rc1 includes:
Full changelog -- https://github.com/nginxinc/kubernetes-ingress/blob/v1.7.0-rc1/CHANGELOG.md#170---release-candidate-1
UPGRADE:
deployments/helm-chart
folder.RESOURCES:
Published by lucacome over 4 years ago
CHANGES:
HELM CHART:
UPGRADE:
nginx/nginx-ingress:1.6.3
or nginx/nginx-ingress:1.6.3-alpine
RESOURCES:
Published by Dean-Coakley over 4 years ago
CHANGES:
HELM CHART:
UPGRADE:
nginx/nginx-ingress:1.6.2
or nginx/nginx-ingress:1.6.2-alpine
RESOURCES: