edge-20.5.3

• Controller

  • Added a Grafana dashboard for tracking multi-cluster traffic metrics
  • Added health checks for the Grafana add-on, under a separate section
  • Fixed issues when updating a remote multi-cluster gateway

• Proxy

  • Added special special handling for I/O errors in HTTP responses so that an
    errno label is included to describe the underlying errors in the proxy's
    metrics

• Internal

  • Started gathering stats of CI runs for aggregating CI health metrics

edge-20.5.2

This edge release contains everything required to get up and running with
multicluster. For a tutorial on how to do that, check out the
documentation.

• CLI
  • Added a section to the linkerd check that validates that all
    clusters part of a multicluster setup have compatible trust anchors
  • Modified the linkerd cluster export-service command to work by
    transforming yaml instead of modifying cluster state
  • Added functionality that allows the linkerd cluster export-service
    command to operate on lists of services
• Controller
  • Changed the multicluster gateway to always require TLS on connections
    originating from outside the cluster
  • Removed admin server timeouts from control plane components, thereby
    fixing a bug that can cause liveness checks to fail
• Helm
  • Moved Grafana templates into a separate add-on chart
• Proxy
  • Improved latency under high-concurrency use cases.

edge-20.5.1

• CLI
  • Fixed all commands to use kubeconfig's default namespace if specified
    (thanks @Matei207!)
  • Added multicluster checks to the linkerd check command
  • Hid development flags in the linkerd install command for release builds
• Controller
  • Added ability to configure Prometheus Altermanager as well as recording
    and alerting rules on the Linkerd Prometheus (thanks @naseemkullah!)
  • Added ability to add more commandline flags to the Prometheus command
    (thanks @naseemkullah!)
• Web UI
  • Fixed TrafficSplit detail page not loading
  • Added Jaeger links to the dashboard when the tracing addon is enabled
• Proxy
  • Modified internal buffering to avoid idling out services as a request
    arrives, fixing failures for requests that are sent exactly once per
    minute--such as Prometheus scrapes

edge-20.4.5

This edge release includes several new CLI commands for use with multi-cluster
gateways, and adds liveness checks and metrics for gateways. Additionally, it
makes the proxy's gRPC error-handling behavior more consistent with other
implementations, and includes a fix for a bug in the web UI.

• CLI
  • Added linkerd cluster setup-remote command for setting up a multi-cluster
    gateway
  • Added linkerd cluster gateways command to display stats for multi-cluster
    gateways
  • Changed linkerd cluster export-service to modify a provided YAML file and
    output it, rather than mutating the cluster
• Controller
  • Added liveness checks and Prometheus metrics for multi-cluster gateways
  • Changed the proxy injector to configure proxies to do destination lookups
    for IPs in the private IP range
• Web UI
  • Fixed errors when viewing resource detail pages
• Internal
  • Created script and config to build a Linkerd CLI Chocolatey package for
    Windows users, which will be published with stable releases (thanks to
    @drholmie!)
• Proxy
  • Changed the proxy to set a grpc-status: UNAVAILABLE trailer when a gRPC
    response stream is interrupted by a transport error

edge-20.4.4

This edge release fixes a packaging issue in edge-20.4.3.

From edge.20.4.3 release notes:

This edge release adds functionality to the CLI to output more detail and
includes changes which support the multi-cluster functionality. Also, the helm
support has been expanded to make installation more configurable. Finally, the
HA reliability is improved by ensuring that control plane pods are restarted
with a rolling strategy

• CLI
  • Added output to the linkerd check --proxy command to list all data
    plane pods which are not up-to-date rather than just printing the first
    one it encounters
  • Added a --proxy flag to the linkerd version command which lists all
    proxy versions running in the cluster and the number of pods running
    each version
  • Lifted requirement of using --unmeshed for linkerd stat when querying
    TrafficSplit resources
  • Added support for multi-stage installs with Add-Ons
• Controller
  • Added a rolling update strategy to Linkerd deployments that have
    multiple replicas during HA deployments to ensure that at most
    one pod begins terminating before a new pod ready is ready
  • Added a new label for the proxy injector to write to the template,
    linkerd.io/workload-ns which indicates the namespace of the workload/pod
• Internal
  • Added a security policy
    to facilitate conversations around security
• Helm
  • Changed charts to use downwardAPI to mount labels to the proxy container
    making them easier to identify
• Proxy
  • Changed the Linkerd proxy endpoint for liveness to use the new /live admin
    endpoint instead of the /metrics endpoint, because the /live endpoint
    returns a smaller payload
  • Added a per-endpoint authority-override feature to support
    multi-cluster gateways

edge-20.4.3

This edge release adds functionality to the CLI to output more detail and
includes changes which support the multi-cluster functionality. Also, the helm
support has been expanded to make installation more configurable. Finally, the
HA reliability is improved by ensuring that control plane pods are restarted
with a rolling strategy

• CLI
  • Added output to the linkerd check --proxy command to list all data
    plane pods which are not up-to-date rather than just printing the first
    one it encounters
  • Added a --proxy flag to the linkerd version command which lists all
    proxy versions running in the cluster and the number of pods running
    each version
  • Lifted requirement of using --unmeshed for linkerd stat when querying
    TrafficSplit resources
  • Added support for multi-stage installs with Add-Ons
• Controller
  • Added a rolling update strategy to Linkerd deployments that have
    multiple replicas during HA deployments to ensure that at most
    one pod begins terminating before a new pod ready is ready
  • Added a new label for the proxy injector to write to the template,
    linkerd.io/workload-ns which indicates the namespace of the workload/pod
• Internal
  • Added a security policy
    to facilitate conversations around security
• Helm
  • Changed charts to use downwardAPI to mount labels to the proxy container
    making them easier to identify
• Proxy
  • Changed the Linkerd proxy endpoint for liveness to use the new /live admin
    endpoint instead of the /metrics endpoint, because the /live endpoint
    returns a smaller payload
  • Added a per-endpoint authority-override feature to support
    mutli-cluster gateways

edge-20.4.2

This release brings a number of CLI fixes and Controller improvements.

• CLI
  • Fixed a bug that caused pods to crash after upgrade if
    --skip-outbound-ports or --skip-inbound-ports were used
  • Added unmeshed flag to the stat command, such that unmeshed resources
    are only displayed if the user opts-in
  • Added a --smi-metrics flag to install, to allow installation of the
    experimental linkerd-smi-metrics component
  • Fixed a bug in linkerd stat, causing incorrect output formatting when using
    the --o wide flag
  • Fixed a bug, causing linkerd uninstall to fail when attempting to delete
    PSPs
• Controller
  • Improved the anti-affinity of linkerd-smi-metrics deployment to avoid
    pod scheduling problems during upgrade
  • Improved endpoints change detection in the linkerd-destination service, enabling
    mirrored remote services to change cluster gateways
  • Added operationID field to tap OpenAPI response to prevent issues during
    upgrade from 2.6 to 2.7
• Proxy
  • Added a new protocol detection timeout to prevent clients from consuming
    resources indefinitely when not sending any data

stable-2.7.1

This release introduces substantial proxy improvements, resulting from continued
profiling & performance analysis. Also support for Kubernetes 1.17 was improved.

To install this release, run: curl https://run.linkerd.io/install | sh

Full release notes:

• CLI
  • Relaxed the clock skew check to match the default node heartbeat interval on
    Kubernetes 1.17 and made this check a warning
• Proxy
  • Fixed a bug that could cause log levels to be processed incorrectly
  • Fixed a bug that could cause the proxy's load balancer to stop processing
    updates from service discovery
  • Removed the inbound router's default capacity to accommodate environments
    that have a high cardinality of virtual hosts served by a single pod
  • Added request_errors_total metric exposing the number of requests that
    receive synthesized responses due to proxy errors

edge-20.4.1

This release introduces some cool new functionalities, all provided by our
awesome community of contributors! Also two bugs were fixed that were introduced
since edge-20.3.2.

• CLI
  • Added linkerd uninstall command to uninstall the control plane (thanks
    @Matei207!)
  • Fixed a bug causing linkerd routes -o wide to not show the proper actual
    success rate
• Controller
  • Fail proxy injection if the pod spec has automountServiceAccountToken
    disabled (thanks @mayankshah1607!)
• Web UI
  • Added a route dashboard to Grafana (thanks @lundbird!)
• Proxy
  • Fixed a bug causing the proxy's inbound to spuriously return 503 timeouts

edge-20.3.4

This release introduces several fixes and improvements to the CLI.

• CLI
  • Added support for kubectl-style label selectors in many CLI commands (thanks
    @mayankshah1607!)
  • Fixed the path regex in service profiles generated from proto files without
    a package name (thanks @amariampolskiy!)
  • Fixed an error when injecting Cronjobs that have no metadata
  • Relaxed the clock skew check to match the default node heartbeat interval
    on Kubernetes 1.17 and made this check a warning
  • Fixed a bug where the linkerd-smi-metrics pod could not be created on
    clusters with pod security policy enabled
• Internal
  • Upgraded tracing components to more recent versions and improved resource
    defaults (thanks @Pothulapati!)