knative/serving knative-v1.0.2 on GitHub

🚨 Breaking or Notable

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:
1. Set the namespace-wildcard-cert-selector to the value:
```
matchExpressions:
 - key: "networking.knative.dev/disableWildcardCert"
   operator: "NotIn"
   values: ["true"]
```
2. 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. (knative/pkg#2436, @dprotaso)

Per-namespace wildcard certificate provisioning has been integrated into the main
Knative controllers and is no longer a separate install. It is now controlled by a
label selector on Kubernetes namespaces.
A new experimental feature, "concurrencyStateEndpoint", allows a webhook to be informed when a container's concurrency goes to/from zero (#11802, #12162, #11917, @psschwei)
When mesh compatibility mode is not set to "auto" in the networking config map,
the activator will respect Kubernetes's readiness state and avoid probing when
kubernetes readiness propagates more quickly than the activator's probe. (#12086, @julz)

Fixes an issue where TLS certificates are requested before domain-ownership is established. (#12080, @mattmoor)

Nothing has changed.

Nothing has changed.