Skip to content

标签

标签使您能够将历史中的特定点标记为重要点
  • edge-24.4.5
  • edge-24.4.4
    ce44897d · proxy: v2.227.1 (#12464) ·
  • edge-24.4.3
  • edge-24.4.2
  • edge-24.4.1
  • edge-24.3.5
  • edge-24.3.4
  • edge-24.3.3
  • edge-24.3.2
  • edge-24.3.1
  • edge-24.2.5
  • edge-24.2.4
    f0d861ea · edge-24.2.4 (#12113) ·
  • version-2.15
    f0d861ea · edge-24.2.4 (#12113) ·
  • stable-2.14.10
    1ea6b271 · stable 2.14.10 (#12111) ·
    This stable release back-ports bugfixes and improvements from recent edge
    releases.
    
    * Introduced support for arbitrary labels in the `podMonitors` field in the
      control plane Helm chart (thanks @jseiser!) ([#11222]; fixes [#11175])
    * Added a `prometheusUrl` field for the heartbeat job in the control plane Helm
      chart (thanks @david972!) ([#11343]; fixes [#11342])
    * Updated the Destination controller to return `INVALID_ARGUMENT` status codes
      properly when a `ServiceProfile` is requested for a service that does not
      exist. ([#11980])
    * Reduced the load on the Destination controller by only processing Server
      updates on workloads affected by the Server ([#12017])
    * Changed how updates to a `Server` selector are handled in the destination
      service. When a `Server` that marks a port as opaque no longer selects a
      resource, the resource's opaqueness will reverted to default settings
      ([#12031]; fixes [#11995])
    * Fixed a race condition in the destination service that could cause panics
      under very specific conditions ([#12022]; fixes [#12010])
    * Fixed an issue where inbound policy could be incorrect after certain policy
      resources are deleted ([#12088])
    
    [#11222]: https://github.com/linkerd/linkerd2/pull/11222
    [#11175]: https://github.com/linkerd/linkerd2/issues/11175
    [#11343]: https://github.com/linkerd/linkerd2/pull/11343
    [#11342]: https://github.com/linkerd/linkerd2/issues/11342
    [#11980]: https://github.com/linkerd/linkerd2/pull/11980
    [#12017]: https://github.com/linkerd/linkerd2/pull/12017
    [#11995]: https://github.com/linkerd/linkerd2/issues/11995
    [#12031]: https://github.com/linkerd/linkerd2/pull/12031
    [#12010]: https://github.com/linkerd/linkerd2/issues/12010
    [#12022]: https://github.com/linkerd/linkerd2/pull/12022
    [#12088]: https://github.com/linkerd/linkerd2/pull/12088
    
  • edge-24.2.3
    42cbf8fd · edge 24.2.3 (#12087) ·
    * Allowed the `MutatingWebhookConfig` timeout value to be configured ([#12028])
      (thanks @mikebell90)
    * Added a counter for items dropped from destination controller workqueue
      ([#12079])
    * Fixed a spurious `linkerd check` error when using container images with
      digests ([#12059])
    * Fixed an issue where inbound policy could be incorrect after certain policy
      resources are deleted ([#12088])
    
    [#12028]: https://github.com/linkerd/linkerd2/pull/12028
    [#12079]: https://github.com/linkerd/linkerd2/pull/12079
    [#12059]: https://github.com/linkerd/linkerd2/pull/12059
    [#12088]: https://github.com/linkerd/linkerd2/pull/12088
    
  • edge-24.2.2
    3073c406 · edge-24.2.2 (#12053) ·
    This release addresses some issues in the destination service that could cause
    it to behave unexpectedly when processing updates.
    
    * Fixed a race condition in the destination service that could cause panics
      under very specific conditions ([#12022]; fixes [#12010])
    * Changed how updates to a `Server` selector are handled in the destination
      service. When a `Server` that marks a port as opaque no longer selects a
      resource, the resource's opaqueness will reverted to default settings
      ([#12031]; fixes [#11995])
    * Introduced Helm configuration values for liveness and readiness probe
      timeouts and delays ([#11458]; fixes [#11453]) (thanks @jan-kantert!)
    
    [#12010]: https://github.com/linkerd/linkerd2/issues/12010
    [#12022]: https://github.com/linkerd/linkerd2/pull/12022
    [#11995]: https://github.com/linkerd/linkerd2/issues/11995
    [#12031]: https://github.com/linkerd/linkerd2/pull/12031
    [#11453]: https://github.com/linkerd/linkerd2/issues/11453
    [#11458]: https://github.com/linkerd/linkerd2/pull/11458
    
  • edge-24.2.1
    ## edge-24.2.1
    
    This edge release contains performance and stability improvements to the
    Destination controller, and continues stabilizing support for ExternalWorkloads.
    
    * Reduced the load on the Destination controller by only processing Server
      updates on workloads affected by the Server ([#12017])
    * Changed how the Destination controller reacts to target clusters (in
      multicluster pod-to-pod mode) whose Server CRD is outdated: skip them and log
      an error instead of panicking ([#12008])
    * Improved the leader election of the ExternalWorkloads Endpoints controller to
      avoid missing events ([#12021])
    * Improved naming of EndpointSlices generated by ExternWorkloads ([#12016])
    * Restriced the number of IPs an ExternalWorkload can have ([#12026])
    
    [#12017]: https://github.com/linkerd/linkerd2/pull/12017
    [#12008]: https://github.com/linkerd/linkerd2/pull/12008
    [#12021]: https://github.com/linkerd/linkerd2/pull/12021
    [#12016]: https://github.com/linkerd/linkerd2/pull/12016
    [#12026]: https://github.com/linkerd/linkerd2/pull/12026
    -----BEGIN SSH SIGNATURE-----
    U1NIU0lHAAAAAQAAADMAAAALc3NoLWVkMjU1MTkAAAAgKsHYzTTiJc883LmaPRYSoBhwFm
    oAaV1b0j4q1C1YYDsAAAADZ2l0AAAAAAAAAAZzaGE1MTIAAABTAAAAC3NzaC1lZDI1NTE5
    AAAAQN3OjUlDDUkTkwUTNxOQKXN1KXprUWzn06Xl+8vOfQT+AK1aIE5GtBV7JXmtj8Ojf4
    uZKysw1rvxVXATAkUwPgM=
    -----END SSH SIGNATURE-----
  • edge-24.1.3
    4e4ff032 · edge-24.1.3 (#11994) ·
  • edge-24.1.2
    38777c7b · edge-24.1.2 (#11951) ·
    This edge release incrementally improves support for ExternalWorkload resources
    throughout the control plane.
    
  • stable-2.14.9
    2aae59bd · 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]).
    
    [#11699]: https://github.com/linkerd/linkerd2/pull/11699
    [#11907]: https://github.com/linkerd/linkerd2/pull/11907
    [#11816]: https://github.com/linkerd/linkerd2/pull/11816