Skip to content

NGINX Ingress Controller - v1.0.2
Compare
Choose a tag to compare
@rikatz rikatz released this 27 Sep 03:30
· 1430 commits to main since this release
controller-v1.0.2
3eb5ec2
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Ingress NGINX v1.0.2 is HERE! Special thanks for @tao12345666333 and @doujiang24 for helping us with coredump issue! You are true heroes! We expect this release solves the problem for all users.

This is a breaking change between previous v0.X branch

This release only supports Kubernetes versions >= v1.19. The support for Ingress Object in networking.k8s.io/v1beta is being dropped and manifests should now use networking.k8s.io/v1.

Please take a look into Migration docs: https://kubernetes.github.io/ingress-nginx/#faq-migration-to-apiversion-networkingk8siov1

Image:
k8s.gcr.io/ingress-nginx/controller:v1.0.2@sha256:85b53b493d6d658d8c013449223b0ffd739c76d76dc9bf9000786669ec04e049

Known Issues

  • Ingress controller now (starting from v1.0.0) mandates cluster scoped access to IngressClass. This leads to problems when updating old Ingress controller to newest version, as described here. We plan to fix it in v1.0.3, see this.

Changes:

  • #7706 Add build info on prometheus metrics
  • #7702 Upgrade lua-resty-balancer to v0.04
  • #7696 Add canary backend name for requests metrics

Contributors

doujiang24 and tao12345666333
Assets 2