Changes since 1.7.3

• Rebuilt with go1.19.4 - see CVE details https://groups.google.com/g/golang-announce/c/L_3rmdT0BMU

Changes since 1.7.2

• Scaling to zero now works when target-burst-capacity is zero. (#13503, @dprotaso)
• Fix a nil pointer panic in the queue proxy when draining (knative/pkg#2645, @dprotaso)

Changes since 1.6

🚨 Notable

Prior RevisionSpec.TimeoutSeconds would cause a request to timeout if the user container returned no response in the allotted time. This would allow for apps to return some data and then remain open forever indefinitely. This prior behaviour was not conformant to the Knative Serving API specification.

In this release we've fixed this behaviour and provided additional knobs to allow users greater control of various timings.

• Revision timeouts now has three knobs for users to control (#12970, @nader-ziada)
  • TimeoutSeconds represents the max duration a request can take
  • ResponseStartTimeoutSeconds is the timeout allowed before a request starts responding
  • IdleTimeoutSeconds is the max duration a request can remain open without getting any data.

💫 New Features & Changes

• Adds a autoscaling.knative.dev/activation-scale annotation that allows the user to set a minimum number of replicas when not scaled to zero. Note that the initial target scale for a revision is still handled by initial-scale; activation-scale will only apply on subsequent scales from zero. (#13161, @psschwei)

🐞Bug Fixes

• Allow upgrades if you revision-timeout-seconds in the ConfigMap config-defaults is configured below 300 (@dprotaso)
• Readiness probes no longer fail if the user container is restarted (due to a liveness probe failure) (#13229, @dprotaso)

🧹 Cleanup

• Building Knative Serving requires go v1.18 (#13169, @psschwei)
• Build commit SHA is no longer under kodata in our containers it is now embedded in the binary since we build with go1.18. Use go version -m [binary] to get the same information (#13130, @dprotaso)

Dependencies