Commit
* edge-22.11.3 change notes Besides the notes, this corrects a small point in `RELEASE.md`, and bumps the proxy-init image tag to `v2.1.0`. Note that the entry under `go.mod` wasn't bumped because moving it past v2 requires changes on `linkerd2-proxy-init`'s `go.mod` file, and we're gonna drop that dependency soon anyways. Finally, all the charts got their patch version bumped, except for `linkerd2-cni` that got its minor bumped because of the tolerations default change. ## edge-22.11.3 This edge release fixes connection errors to pods using a `hostPort` different than their `containerPort`. Also the `network-validator` init container improves its logging, and the `linkerd-cni` DaemonSet now gets deployed in all nodes by default. * Fixed `destination` service to properly discover targets using a `hostPort` different than their `containerPort`, which was causing 502 errors * Upgraded the `network-validator` with better logging allowing users to determine whether failures occur as a result of their environment or the tool itself * Added default `Exists` toleration to the `linkerd-cni` DaemonSet, allowing it to be deployed in all nodes by default, regardless of taints Co-authored-by: Oliver Gould <ver@buoyant.io>
- Loading branch information
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.