Kubernetes-based, scale-to-zero, request-driven compute
APACHE-2.0 License
Bot releases are visible (Hide)
Published by knative-prow-releaser-robot about 2 years ago
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.
TimeoutSeconds
represents the max duration a request can takeResponseStartTimeoutSeconds
is the timeout allowed before a request starts respondingIdleTimeoutSeconds
is the max duration a request can remain open without getting any data.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)revision-timeout-seconds
in the ConfigMap config-defaults
is configured below 300
(@dprotaso)go version -m [binary]
to get the same information (#13130, @dprotaso)Nothing has changed.
Nothing has changed.
Published by knative-prow-releaser-robot about 2 years ago
We discovered a bug that prevents upgrades if you configured revision-timeout-seconds
in the ConfigMap config-defaults
to be less than 300
. This was fixed in the subsequent point release.
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.
TimeoutSeconds
represents the max duration a request can takeResponseStartTimeoutSeconds
is the timeout allowed before a request starts respondingIdleTimeoutSeconds
is the max duration a request can remain open without getting any data.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)go version -m [binary]
to get the same information (#13130, @dprotaso)Nothing has changed.
Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
x-kubernetes-preserve-unknown-fields
is now only specified for attributes behind feature flags (#13095, @dprotaso)Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
Published by knative-prow-releaser-robot over 2 years ago
min-scale: "4"
, the revision will not be marked ready until all four pods are ready. Note that revisions may take slightly longer to become ready after this change. See https://knative.dev/docs/serving/autoscaling/scale-bounds/ for more details. (#12811, @psschwei)serving.knative.dev/release
labels, deprecated in v1.3, have been removed. Please switch over to using app.kubernetes.io/name: knative-serving
and app.kubernetes.io/version: $VERSION
. (#12754, @psschwei)serving.knative.dev/progress-deadline
annotation in .spec.template.metadata.annotations
(#12751, @psschwei)Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It has been removed in this release. (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in favour of fixing the behaviour of the existing Timeout
field. (#12635, @dprotaso)app.kubernetes.io
labels (#12587, @psschwei)autoscaling.knative.dev/target
values (#12698, @psschwei)Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in favour of fixing the behaviour of the existing Timeout
field. (#12635, @dprotaso)app.kubernetes.io
labels (#12587, @psschwei)autoscaling.knative.dev/target
values (#12698, @psschwei)Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It has been removed in this release. (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in favour of fixing the behaviour of the existing Timeout
field. (#12635, @dprotaso)app.kubernetes.io
labels (#12587, @psschwei)autoscaling.knative.dev/target
values (#12698, @psschwei)Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It has been removed in this release. (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
Release Notes
Serving
Published by knative-prow-releaser-robot over 2 years ago
The per-namespace wildcard certificate provisioner has been integrated into the base controllers
and is now controlled by the namespace-wildcard-cert-selector field. This field allows you
to use a Kubernetes LabelSelector to choose which namespaces should have certificates
provisioned.
To migrate existing usage of the serving-nscert controller, do the following:
Set the namespace-wildcard-cert-selector to the value:
matchExpressions:
- key: "networking.knative.dev/disableWildcardCert"
operator: "NotIn"
values: ["true"]
Remove the Deployment, Service and ClusterRole defined by the serving-nscert.yaml resources
in the previous release. (#12174, @evankanderson)
Controllers now properly shut down and relinquish their K8s leases. This fixes potential dropped traffic during upgrades. (https://github.com/knative/pkg/issues/2436, @dprotaso)
Nothing has changed.
Nothing has changed.
Published by knative-prow-releaser-robot over 2 years ago
Allow users to set container[*].securityContext.runAsGroup (#12003, @dprotaso)
A new setting, mesh-compatibility-mode
, in the networking config map allows an administrator
to explicitly tell Activator and Autoscaler to use Direct Pod IP (most efficient, but not compatible
with mesh being enabled), Cluster IP (less efficient, but needed if mesh is enabled), or to
Autodetect (the current behaviour, and the default, causes Activator and Autoscaler to first attempt
Direct Pod IP communication, and then fall back to Cluster IP if it sees a mesh-related error status
code). (#11999, @julz)
Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It has been removed in this release. (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
Release Notes
Serving
Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It is present in this release but has been removed in v1.2.2 (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
RevisionSpec.MaxDurationSeconds
in error. It has been removed in v1.2.2 (https://github.com/knative/serving/issues/12634, @dprotaso)periodSeconds
for readiness probe to Kuberentes default (10s) (#12550, @psschwei)kubernetes.podspec-persistent-volume-claim
kubernetes.podspec-persistent-volume-write
(#12458, @skonto)Published by knative-prow-releaser-robot over 2 years ago
Release Notes
Serving
Published by knative-prow-releaser-robot almost 3 years ago
Release Notes
Serving