Skip to content

v2.0.4

Latest
Compare
Choose a tag to compare
@johnlanni johnlanni released this 06 Dec 05:53
· 11 commits to main since this release
85c7b1f

Recommended Upgrade Reasons

Basic capability update

  1. Support for wildcard domain routing with exact domain fallback

As in the example below, in the previous version, when requesting www.example.com/abcd , if no route was found under www.example.com , it would directly return a 404; in the current version, if no route is found under www.example.com , it will then find route under *.example.com .

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: wildcard-ingress
spec:
  rules:
  - host: "*.example.com"
    http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: wildcard-service
            port:
              number: 80
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: exact-ingress
spec:
  rules:
  - host: "www.example.com"
    http:
      paths:
      - path: /abc
        pathType: Exact
        backend:
          service:
            name: exact-service
            port:
              number: 80

‼️ Important Fixes

  1. In the previous 2.x versions, due to issues with the RDS caching strategy, the latest configuration might not have been distributed during high-frequency updates of the ingress. #1547
  2. The previous 2.x version did not automatically configure the number of Envoy worker threads based on the cpu request/limit.

What's Changed

New Contributors

Full Changelog: v2.0.2...v2.0.4