Skip to content
This repository has been archived by the owner on May 24, 2023. It is now read-only.

Releases: nginxinc/nginx-ingress-operator

v0.5.1

01 Mar 22:55
f34d729
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.5.1

🔨 Maintenance

⬆️ Dependencies

Compatibility

  • NGINX Ingress Controller 2.1.1
  • Openshift 4.6 or newer.

v0.5.0

13 Jan 00:42
07d9f5d
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.5.0

🚀 Features

🐛 Bug Fixes

📝 Documentation

🔨 Maintenance

⬆️ Dependencies

Compatibility

  • NGINX Ingress Controller 2.1.0
  • Openshift 4.6 or newer.

v0.4.0

06 Oct 16:35
5cafbf5
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.4.0

🚀 Features

  • Replace v1beta1 with v1 and remove uses of flag 'use-ingress-class (#151) @soneillf5

🐛 Bug Fixes

📝 Documentation

🔨 Maintenance

⬆️ Dependencies

Compatibility

  • NGINX Ingress Controller 2.0.0
  • Openshift 4.6 or newer.

v0.3.0

13 Jul 12:39
550b9c2
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.3.0

🚀 Features

🐛 Bug Fixes

📝 Documentation

🔨 Maintenance

⬆️ Dependencies

Compatibility

  • NGINX Ingress Controller 1.12.0
  • Openshift 4.5 or newer.

Upgrade instructions

Please see the upgrade docs here

v0.2.0

21 Apr 22:55
765947b
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.2.0

🐛 Bug Fixes

📝 Documentation

🔨 Maintenance

⬆️ Dependencies

Known Issues

  • The Operator doesn't automatically remove IngressClasses created by #29. Issue is tracked in #88

Compatibility

  • NGINX Ingress Controller 1.11.x
  • Openshift 4.5 or newer.

v0.1.0

10 Mar 16:05
4a21fa2
Compare
Choose a tag to compare

New in NGINX Ingress Operator v0.1.0

🚀 Features

🐛 Bug Fixes

📝 Documentation

🔨 Maintenance

Known Issues:

The Operator doesn't automatically remove IngressClasses created by #29. Issue is tracked in #88

Compatibility

  • NGINX Ingress Controller 1.10.x
  • Openshift 4.5 or newer.

Upgrade Instructions:

  1. Remove the existing Policy CRD: kubectl delete crd policies.k8s.nginx.org
    Please note that deletion of the policies.k8s.nginx.org CRD will result in all instances of that CRD being deleted too. Ensure to back up any important Custom Resource instances first!
  2. Delete the existing SCC: kubectl delete scc nginx-ingress-scc
  3. Upgrade the operator to version 0.1.0.
  4. If the defaultSecret field is not set in your nginxingresscontrollers.k8s.nginx.org resource (or resources):
    1. Remove the generated default secret. For example: kubectl delete secret -n my-nginx-ingress my-nginx-ingress-controller
    2. Wait until the operator regenerates the secret. The old secret was of the type Opaque. The new secret will be of the type kubernetes.io/tls.
  5. Alternatively, if the defaultSecret is set to some secret, make sure it is of the type kubernetes.io/tls. If not, recreate the secret with the type kubernetes.io/tls.
  6. If the wildcardTLS is set to some secret, make sure it is of the type kubernetes.io/tls. If not, recreate the secret with the type kubernetes.io/tls.
  7. Ensure that the TLS secrets referenced by Ingress, VirtualServer and Policy resources are of the type kubernetes.io/tls, JWT secrets are of the type nginx.org/jwt and CA secrets are of the type nginx.org/ca. To avoid potential disruption of client traffic, instead of recreating the secrets, create new secrets with the correct type and update the Ingress, VirtualServer and Policy resources to use the new secrets.
  8. Update any existing instances of the nginxingresscontrollers.k8s.nginx.org Custom Resource to use an NGINX Ingress Controller 1.10.x image.

Note: Steps 4-8 are required because Version 1.10.0 of the Ingress Controller added a requirement for secrets to be one of the following types: kubernetes.io/tls for TLS secrets; nginx.org/jwk for JWK secrets; or nginx.org/ca for CA secrets. Please see the section UPDATING SECRETS in https://docs.nginx.com/nginx-ingress-controller/releases/#nginx-ingress-controller-1-10-0 for more details.

NGINX Ingress Operator 0.0.7

11 Dec 22:53
1f0e9f7
Compare
Choose a tag to compare

FEATURES:

  • 29 Add IngressClass support.
  • 26 Add mTLS policy support.
  • 25 Add JWT policy support.
  • 21 Add latency metrics support.
  • 18 Add support for policies in VS routes and VSR subroutes. Add RateLimit policy support

FIXES:

  • 31 Add Status update for VS/VSR to RBAC.

KNOWN ISSUES:

  • The Operator doesn't automatically remove IngressClasses created by 29

COMPATIBILITY:

  • NGINX Ingress Controller 1.9.x.
  • Openshift 4.5 or newer.

NGINX Ingress Operator 0.0.6

04 Aug 15:50
22d32ce
Compare
Choose a tag to compare

FEATURES:

  • 13 Add support for App Protect.
  • 11 Add enableSnippets cli argument support.

IMPROVEMENTS:

  • 15 Downgrade operator-sdk to 0.17.
  • 14 Add KIC supported versions to README.
  • 12 Make operator install KIC CRDs from manifests.
  • 10 Update operator-sdk to 0.18.
  • 8 Update go to 1.14.
  • 7 Update makefile to include all manifests.

COMPATIBILITY:

  • NGINX Ingress Controller 1.8.x.
  • Openshift 4.3 or newer.

NGINX Ingress Operator 0.0.4

23 Apr 13:57
Compare
Choose a tag to compare

FEATURES:

  • 4 Add new CRDs for NGINX Ingress Controller 1.7.0
  • 5 Make NGINX Ingress Operator RedHat certified. Learn more about certified operators for Openshift here.

COMPATIBILITY:

  • NGINX Ingress Controller 1.7.x.
  • Openshift 4.3 or newer.