Kubernetes-based, scale-to-zero, request-driven compute
APACHE-2.0 License
Bot releases are visible (Hide)
Published by knative-prow-releaser-robot over 3 years ago
autocreateClusterDomainClaims
flag to network config map. (networking#330, @julz)Nothing has changed.
Nothing has changed.
Published by knative-prow-releaser-robot over 3 years ago
ReadOnlyRootFilesystem
on the container's SecurityContext
(#10560, @senthilnathan)FailureThreshold
& TimeoutSeconds
are now defaulted to 3
and 1
respectively when a user opts into non-aggressive probing (ie. PeriodTimeout
> 1) (#10700, @shinigambit)serving.knative.dev/rolloutDuration
annotation, (#10561, @vagababov et al.)Published by knative-prow-releaser-robot over 3 years ago
{name}.{namespace}.svc.{cluster-suffix}
. (#10210, @julz)serving.knative.dev/domainmapping
label for Ingress generated by DomainMapping. (#10370, @nak3)PROFILING_PORT
(knative/pkg#1950, @mattmoor)rolloutDuration
entry in the config-network
configmap. When positive this setting will move the traffic gradually from the previous to the current revision over this period of time. It can handle several rollouts at the same time in three dimensions:
Published by knative-prow-releaser-robot almost 4 years ago
{name}.{namespace}.svc.{cluster-suffix}
. (#10210, @julz)serving.knative.dev/domainmapping
label for Ingress generated by DomainMapping. (#10370, @nak3)PROFILING_PORT
(knative/pkg#1950, @mattmoor)rolloutDuration
entry in the config-network
configmap. When positive this setting will move the traffic gradually from the previous to the current revision over this period of time. It can handle several rollouts at the same time in three dimensions:
Published by knative-prow-releaser-robot almost 4 years ago
This bundle was deprecated in our 0.14 release and will be removed in our next release
EnableVarLogCollection
behaviourWe always mount a emptyDir volume at /var/log
in our user-containers. This impacts some popular containers images (ie. nginx) preventing them from starting.
In the next release (v0.19) we plan on changing this default behaviour and only mount a volume when EnableVarLogCollection
is set to true
.
Please reach out in https://github.com/knative/serving/issues/7881 if you have issues/comments about the approach & timeline.
tagHeaderBasedRouting
flag in config-network
is moved to config-features
as tag-header-based-routing
. (#8856, @igsong)Published by knative-prow-releaser-robot almost 4 years ago
v1alpha1
and v1beta1
APIs (#9617, #9620, @mattmoor, @dprotaso)/var/log
if the operator has enabled log collection/var/log
requirement has changed from MUST
to MAY
(#9683, @dprotaso)Published by knative-prow-releaser-robot almost 4 years ago
This bundle was deprecated in our 0.14 release and will be removed in our next release
EnableVarLogCollection
behaviourWe always mount a emptyDir volume at /var/log
in our user-containers. This impacts some popular containers images (ie. nginx) preventing them from starting.
In the next release (v0.19) we plan on changing this default behaviour and only mount a volume when EnableVarLogCollection
is set to true
.
Please reach out in https://github.com/knative/serving/issues/7881 if you have issues/comments about the approach & timeline.
tagHeaderBasedRouting
flag in config-network
is moved to config-features
as tag-header-based-routing
. (#8856, @igsong)Published by knative-prow-releaser-robot almost 4 years ago
This bundle was deprecated in our 0.14 release and will be removed in our next release
EnableVarLogCollection
behaviourWe always mount a emptyDir volume at /var/log
in our user-containers. This impacts some popular containers images (ie. nginx) preventing them from starting.
In the next release (v0.19) we plan on changing this default behaviour and only mount a volume when EnableVarLogCollection
is set to true
.
Please reach out in https://github.com/knative/serving/issues/7881 if you have issues/comments about the approach & timeline.
tagHeaderBasedRouting
flag in config-network
is moved to config-features
as tag-header-based-routing
. (#8856, @igsong)Published by knative-prow-releaser-robot almost 4 years ago
There is a new annotation that can be used to control the number of pods that are initially deployed when new Revisions are rolled out.
In addition to net-istio, we now have three networking layers that we classify as (at least) Beta.
It remains 1.16, but we may bump to 1.17 in the coming release depending on its availability for qualification testing (per our release principles).
--disable-ha
.Published by knative-prow-releaser-robot about 4 years ago
This bundle was deprecated in our 0.14 release and will be removed in our next release
EnableVarLogCollection
behaviourWe always mount a emptyDir volume at /var/log
in our user-containers. This impacts some popular containers images (ie. nginx) preventing them from starting.
In the next release (v0.19) we plan on changing this default behaviour and only mount a volume when EnableVarLogCollection
is set to true
.
Please reach out in https://github.com/knative/serving/issues/7881 if you have issues/comments about the approach & timeline.
tagHeaderBasedRouting
flag in config-network
is moved to config-features
as tag-header-based-routing
. (#8856, @igsong)Published by knative-prow-releaser-robot about 4 years ago
There is a new annotation that can be used to control the number of pods that are initially deployed when new Revisions are rolled out.
In addition to net-istio, we now have three networking layers that we classify as (at least) Beta.
It remains 1.16, but we may bump to 1.17 in the coming release depending on its availability for qualification testing (per our release principles).
--disable-ha
.Published by knative-prow-releaser-robot about 4 years ago
There is a new annotation that can be used to control the number of pods that are initially deployed when new Revisions are rolled out.
In addition to net-istio, we now have three networking layers that we classify as (at least) Beta.
It remains 1.16, but we may bump to 1.17 in the coming release depending on its availability for qualification testing (per our release principles).
--disable-ha
.Published by knative-prow-releaser-robot about 4 years ago
go mod
migrationKnative is now completely migrated to Golang modules.
serving.yaml
and serving-cert-manager.yaml
will be shipped for the last time in this release. They have been broken out into separate artifacts. Please refer to the current installation docs for guidance on how to install Knative Serving and its optional components.
As per the Kubernetes minimum version principle - our current minimum supported Kubernetes version is now 1.16.
We compute a subset of Activator pods for each revision in a consistent manner, rather than assigning all. This noticeably improves load balancing for smaller revisions with small container concurrency values.
Revision.Status.ImageDigest
is deprecated and the digest will appear in Revision.Status.ContainerStatus
.features.knative.dev/podspec-dryrun: enabled
features.knative.dev/podspec-dryrun: strict
concurrencyModel
#7893 (thanks @vagabov)buildName
and buildRef
#7896 (thanks @vagabov)user-container
.Published by knative-prow-releaser-robot about 4 years ago
There is a new annotation that can be used to control the number of pods that are initially deployed when new Revisions are rolled out.
In addition to net-istio, we now have three networking layers that we classify as (at least) Beta.
It remains 1.16, but we may bump to 1.17 in the coming release depending on its availability for qualification testing (per our release principles).
--disable-ha
.Published by knative-prow-releaser-robot about 4 years ago
There is a new annotation that can be used to control the number of pods that are initially deployed when new Revisions are rolled out.
In addition to net-istio, we now have three networking layers that we classify as (at least) Beta.
It remains 1.16, but we may bump to 1.17 in the coming release depending on its availability for qualification testing (per our release principles).
--disable-ha
.Published by knative-prow-releaser-robot about 4 years ago
We have made the decision to deprecate the bundled monitoring tools that have remained unchanged since 2018 due to a lack of community interest. We will stop releasing them in a coming release and will instead focus on documenting how to integrate with existing monitoring systems using OpenTelemetry.
We have included a new migration Job to migrate existing resources. See the serving-storage-version-migration.yaml release artifact.
We were unable to bump our minimum Kubernetes dependency to 1.16 this release as planned due to its lack of availability in GKE (on which we have a hard dependency for CI/CD). The principle behind our choice of minimum upstream version remains the same, and users should expect future releases to attempt to βcatch upβ.
After installing 0.14, a new migration Job must be run to migrate pre-existing resources, and remove v1alpha1 as a stored version from our CRDs.
Fixes a long-standing issue where our tag resolutions does not work properly for AWS ECR.
Istio KIngress reconciler is now separated into its own repository knative/net-istio, enabling more focused testing on presubmits. In the future, Istio integration bugs should be filed to this new repository
knative/net-http01 is a simple standalone ACME HTTP01 solver for the Knative Certificate abstraction.
A new home for Kourier - a lightweight Envoy-based Knative Ingress reconciler previously hosted at https://github.com/3scale/kourier.
Adding Istio canonical service labels (https://github.com/istio/istio/pull/20943) to Knative objects for better integration with Istio UX.
/healthz
for probe path for easier whitelisting #5918 (thanks itsmurugappa, shreejad)We changed our probe path from /_internal/knative/activator/probe to /healthz and made that consistent across all probe receivers in Knative Serving.
Any scenario where probing would fail forever with the current implementation is now treated as a successful probing, to allow failing-open in cases where users use a 3-legged-oauth setup that would cause probing to fail indefinitely.
Previously, we sometimes referred to unused Gateways in a VirtualService. That caused issues with Istio validation logic if those unused Gateways were non-existent. Unused Gateways are no longer referred from VirtualServices.
Published by knative-prow-releaser-robot over 4 years ago
serving-post-install-jobs.yaml
is expected to be used with kubectl create
- the jobs are idempotentPublished by knative-prow-releaser-robot over 4 years ago
go mod
migrationKnative is now completely migrated to Golang modules.
serving.yaml
and serving-cert-manager.yaml
will be shipped for the last time in this release. They have been broken out into separate artifacts. Please refer to the current installation docs for guidance on how to install Knative Serving and its optional components.
As per the Kubernetes minimum version principle - our current minimum supported Kubernetes version is now 1.16.
We compute a subset of Activator pods for each revision in a consistent manner, rather than assigning all. This noticeably improves load balancing for smaller revisions with small container concurrency values.
Revision.Status.ImageDigest
is deprecated and the digest will appear in Revision.Status.ContainerStatus
.features.knative.dev/podspec-dryrun: enabled
features.knative.dev/podspec-dryrun: strict
concurrencyModel
#7893 (thanks @vagabov)buildName
and buildRef
#7896 (thanks @vagabov)user-container
.Published by knative-prow-releaser-robot over 4 years ago
We have made the decision to deprecate the bundled monitoring tools that have remained unchanged since 2018 due to a lack of community interest. We will stop releasing them in a coming release and will instead focus on documenting how to integrate with existing monitoring systems using OpenTelemetry.
We have included a new migration Job to migrate existing resources. See the serving-storage-version-migration.yaml release artifact.
We were unable to bump our minimum Kubernetes dependency to 1.16 this release as planned due to its lack of availability in GKE (on which we have a hard dependency for CI/CD). The principle behind our choice of minimum upstream version remains the same, and users should expect future releases to attempt to βcatch upβ.
After installing 0.14, a new migration Job must be run to migrate pre-existing resources, and remove v1alpha1 as a stored version from our CRDs.
Fixes a long-standing issue where our tag resolutions does not work properly for AWS ECR.
Istio KIngress reconciler is now separated into its own repository knative/net-istio, enabling more focused testing on presubmits. In the future, Istio integration bugs should be filed to this new repository
knative/net-http01 is a simple standalone ACME HTTP01 solver for the Knative Certificate abstraction.
A new home for Kourier - a lightweight Envoy-based Knative Ingress reconciler previously hosted at https://github.com/3scale/kourier.
Adding Istio canonical service labels (https://github.com/istio/istio/pull/20943) to Knative objects for better integration with Istio UX.
/healthz
for probe path for easier whitelisting #5918 (thanks itsmurugappa, shreejad)We changed our probe path from /_internal/knative/activator/probe to /healthz and made that consistent across all probe receivers in Knative Serving.
Any scenario where probing would fail forever with the current implementation is now treated as a successful probing, to allow failing-open in cases where users use a 3-legged-oauth setup that would cause probing to fail indefinitely.
Previously, we sometimes referred to unused Gateways in a VirtualService. That caused issues with Istio validation logic if those unused Gateways were non-existent. Unused Gateways are no longer referred from VirtualServices.
Published by knative-prow-releaser-robot over 4 years ago
go mod
migrationKnative is now completely migrated to Golang modules.
serving.yaml
and serving-cert-manager.yaml
will be shipped for the last time in this release. They have been broken out into separate artifacts. Please refer to the current installation docs for guidance on how to install Knative Serving and its optional components.
As per the Kubernetes minimum version principle - our current minimum supported Kubernetes version is now 1.16.
We compute a subset of Activator pods for each revision in a consistent manner, rather than assigning all. This noticeably improves load balancing for smaller revisions with small container concurrency values.
Revision.Status.ImageDigest
is deprecated and the digest will appear in Revision.Status.ContainerStatus
.features.knative.dev/podspec-dryrun: enabled
features.knative.dev/podspec-dryrun: strict
concurrencyModel
#7893 (thanks @vagabov)buildName
and buildRef
#7896 (thanks @vagabov)user-container
.