From 2cdcfb7db7e1a685375c2c58bce7ff51be3eb699 Mon Sep 17 00:00:00 2001 From: Flynn Date: Tue, 2 Jul 2024 12:10:39 -0400 Subject: [PATCH] Link to the issue comment explaining init container resource requests. Signed-off-by: Flynn --- .../content/blog/2024/0701-edge-release-roundup.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/linkerd.io/content/blog/2024/0701-edge-release-roundup.md b/linkerd.io/content/blog/2024/0701-edge-release-roundup.md index d59f51b7eb..6ca3c7efe4 100644 --- a/linkerd.io/content/blog/2024/0701-edge-release-roundup.md +++ b/linkerd.io/content/blog/2024/0701-edge-release-roundup.md @@ -70,9 +70,12 @@ can find them in the release notes for each release. This release changes the proxy-init container to always request the same amount of memory and CPU as the proxy itself, and removes the ability to explicitly set proxy-init's requests because there's now no need to do so. -(This doesn't increase the resources required for the pod as a whole, because -the proxy-init container completes before the proxy starts, letting the proxy -reuse resources requested by the proxy-init container.) +(This doesn't increase the resources required for the pod as a +whole, because the proxy-init container completes before the proxy +starts, letting the proxy reuse resources requested by the proxy-init +container. For full details, check out [issue #11320][comment]). + +[comment]: https://github.com/linkerd/linkerd2/issues/11320#issuecomment-2186383081 It also continues work on upcoming GRPCRoute support. Finally, if `proxy.logHTTPHeaders` is somehow empty, it correctly defaults to "off".