knative/serving knative-v1.8.1

Serving v1.8.1

on GitHub

tags: Release Notes Serving

Changes since 1.8.0

• We reverted #13376 - SettingSeccompProfile to RunTimeDefault on the queue-proxy sidecar. This seems to break older OpenShift versions and GKE workloads running on gVisor. We will make this option configurable in the future.
  • See gVisor/GKE issue (google/gvisor#8248, https://issuetracker.google.com/issues/260968397) to allow this value
• 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)

Changelog since 1.7

🚨 Breaking or Notable

• Uses the cluster domain suffix svc.cluster.local as the default domain. As routes using the cluster domain suffix are not exposed through Ingress, users will need to configure DNS in order to expose their services (most users probably already are). (#13259, @psschwei)
• Upgrade HorizontalPodAutoscaler to autoscaling/v2 API version (#13337, @nader-ziada)
• Services may now set seccompProfile in SecurityContext to allow users to comply with the restricted Pod Security Standards best-practice (#13401, @evankanderson)
• Bump min-version to k8s 1.23, so removing kind 1.22 testing (#13357, @nader-ziada)
• Increase the outbound context deadline in reconcilers to 30s (from 10s) to match the maximum K8s webhook timeout. (#13323, @mattmoor)

💫 New Features & Changes

• Add timeout handling in Activator when processing a request for a revision (#13261, @nader-ziada)
• EmptyDir volumes feature flag is now enabled by default (#13405, @dprotaso)
• Save data from perf tests to create a dashboard. (#13192, @nader-ziada)

Bug or Regression

• Knative services can now specify securityContext.allowPrivilegeEscalation (#13395, @mattmoor)
• ConfigMap config-defaults property revision-response-start-timeout-seconds now defaults to revision-timeout-seconds. This should unblock upgrades who set revision-timeout-seconds lower than the default value of 300 (#13255, @dprotaso)
• Fix LatestReadyRevision semantics so it only advances forward. When a Revision fails the Configuration & Route will no longer fall back to older revision. The exception is when you rollback to a Revision that is explicitly named. (#13239, @dprotaso)

Dependencies