edge-24.1.3

edge-24.1.3

This release continues support for ExternalWorkload resources throughout the
control and data planes.

• Updated the proxy to use SPIRE to instrument identity outside of Kubernetes.
• Updated the Destination controller to return INVALID_ARGUMENT status codes
  properly when a ServiceProfile is requested for a service that does not
  exist. (#11980)
• An ExternalWorkload EndpointSlice controller has been added to the
  Destination controller.
• Added a createNamespaceMetadataJob Helm value to control whether the
  namespace-metadata job is run during install (#11782)

stable-2.14.9

stable-2.14.9

This stable release adds a cni-repair-controller which fixes the issue of
injected pods that cannot acquire proper network config because linkerd-cni
and/or the cluster's network CNI haven't fully started (#11699). It also
fixes a bug in the destination controller where having a large number of
Server resources could cause the destination controller to use an excessive
amount of CPU (#11907). Finally, it fixes a conflict with tap resource
shortnames which was causing warnings from kubectl v1.29.0+ (#11816).

edge-24.1.2

edge-24.1.2

This edge release incrementally improves support for ExternalWorkload resources
throughout the control plane.

edge-24.1.1

edge-24.1.1

This edge release introduces a number of different fixes and improvements. More
notably, it introduces a new cni-repair-controller binary to the CNI plugin
image. The controller will automatically restart pods that have not received
their iptables configuration.

• Removed shortnames from Tap API resources to avoid colliding with existing
  Kubernetes resources (#11816; fixes #11784)
• Introduced a new ExternalWorkload CRD to support upcoming mesh expansion
  feature (#11805)
• Changed MeshTLSAuthentication resource validation to allow SPIFFE URI
  identities (#11882)
• Introduced a new cni-repair-controller to the linkerd-cni DaemonSet to
  automatically restart misconfigured pods that are missing iptables rules
  (#11699; fixes #11073)
• Fixed a "duplicate metrics" warning in the multicluster service-mirror
  component (#11875; fixes #11839)
• Added metric labels and weights to linkerd diagnostics endpoints json
  output (#11889)
• Changed how Server updates are handled in the destination service. The
  change will ensure that during a cluster resync, consumers won't be
  overloaded by redundant updates (#11907)
• Changed linkerd install error output to add a newline when a Kubernetes
  client cannot be successfully initialised (#11917)

stable-2.14.8

stable-2.14.8

This stable release fixes an issue in the control plane where discovery for pod
IP addresses could hang indefinitely (#11815).

edge-23.12.4

edge-23.12.4

This edge release includes fixes and improvements to the destination
controller's endpoint resolution API.

• Fixed an issue in the control plane where discovery for pod IP addresses could
  hang indefinitely (#11815)
• Updated the proxy to enforce time limits on control plane response streams so
  that proxies more naturally distribute load over control plane replicas
  (#11837)
• Fixed the policy's controller service metadata responses so that proxy logs
  and metrics have informative values (#11842)

stable-2.14.7

stable-2.14.7

This stable release fixes two bugs in the Linkerd control plane.

• Fixed an issue in the destination controller where the metadata API was not
  properly initialized for jobs, leading to error messages and unnecessary API
  calls (#11541)
• Fixed an issue in the policy controller where it was overriding statuses on
  HTTPRoute resources from other controllers (#11705)

edge-23.12.3

edge-23.12.3

This edge release contains improvements to the logging and diagnostics of the
destination controller.

• Added a control plane metric to count errors talking to the Kubernetes API
  (#11774)
• Fixed an issue causing spurious destination controller error messages for
  profile lookups on unmeshed pods with port in default opaque list (#11550)

edge-23.12.2

edge-23.12.2

This edge release includes a restructuring of the proxy's balancer along with
accompanying new metrics. The new minimum supported Kubernetes version is 1.22.

• Restructured the proxy's balancer (#11750): balancer changes may now occur
  independently of request processing. Fail-fast circuit breaking is enforced on
  the balancer's queue so that requests can't get stuck in a queue indefinitely.
  This new balancer is instrumented with new metrics: request (in-queue) latency
  histograms, failfast states, discovery updates counts, and balancer endpoint
  pool sizes.
• Changed how the policy controller updates HTTPRoute status so that it doesn't
  affect statuses from other non-linkerd controllers (#11705; fixes #11659)

stable-2.14.6

stable-2.14.6

This stable release back-ports bugfixes and improvements from recent edge
releases.

• multicluster: Added an imagePullSecrets configuration to
  linkerd-multicluster Helm chart (thanks @lhaussknecht!). (#11287)
• multicluster: Updated the service mirror to support gateways exposed on
  multiple IP addresses (thanks @MrFreezeex!) (#11499)
• Updated control plane logging so that client-go may emit error logs. This will
  also ensures that all logs are emitted in JSON when the json log format is
  enabled. (#11632)
• Added kubeAPI.clientBurst and kubeAPI.clientQPS configurations that allow
  users to configure the burst and QPS rate limits for the Kubernetes API
  clients used by the control plane. The default burst and qps values are now
  set at 200 and 100, respectively. The prior defaults limited bursts 10 and QPS
  to 5, which could cause throttling issues in clusters that schedule many pods
  quickly. (#11644)
• viz: Update the default prometheus version to v2.48.0. (#11633)