knative/serving v0.25.0

Knative Serving release v0.25.0

on GitHub

🚨 Breaking or Notable

1. Renaming of some net-kourier components

Related issue: knative/networking#448

As part of our efforts to GA/1.0 we've standardized on the naming of our networking plugins that are installed along side Serving. If you're managing your Knative deployment manually with kubectl this will require a two-phase upgrade process. In order to upgrade net-kourier to v0.25.0 using kubectl please follow the steps:

# Apply the new release
$ kubectl apply -f net-kourier.yaml

# Once the deployment is ready apply the same file but 
# prune the old resources
$ kubectl apply -f net-kourier.yaml \
  --prune -l networking.knative.dev/ingress-provider=kourier

2. Disabling namespace certificate provisioning legacy label

The namespace label networking.internal.knative.dev/disableWildcardCert has been deprecated since v0.15.0 release in favour of networking.knative.dev/disableWildcardCert. We have dropped support for this legacy label. (#11626, @nak3)

💫 New Features & Changes

• A feature flag is available to enable priorityClassName for Knative Services. See config-features for details. (#11746, @nealhu)
• Add memory metrics for HPA: hpa.autoscaling.knative.dev (#11668, @zhaojizhuang)
• Added app.kubernetes.io/name labels to resources. It will be replacing app labels in the future. (#11655, @upodroid)
• Containers[*].securityContext.runAsNonRoot can be set to true without a feature flag (#11606, @senthilnathan)
• Users can set spec.template.spec.automountServiceAccountToken to false in a PodSpec in order to opt-out of Kubenetes' default behaviour of mounting a ServiceAccount token in that Pod's containers. (#11723, @psschwei)
• Add v1beta1 version of DomainMapping crd (#11682, @julz)

🐞 Bug Fixes

• Set ENABLE_HTTP2_AUTO_DETECTION to false by default if the feature is not enabled. (#11760, @psschwei)

Dependencies