For the complete documentation index, see llms.txt. This page is also available as Markdown.

How to Configure streamingConnectionIdleTimeout: "672h" Without Dynamic Kubelet Config

Problem

The customisations configured via Dynamic Kubelet Config previously for streamingConnectionIdleTimeout: "672h" is no longer possible __to use since moving to K8s v1.22 cluster on containerd where Dynamic Kubelet Config is deprecated, the setting is not taken into account as compared to docker previously.

Upstream Issues:

Environment

  • Platform9 Managed Kubernetes - v5.6.8 and Higher

Solution

Set the value stream_idle_timeout = "1m"in /etc/containerd/config.toml file for containerd service on the master node, takes into effect when kubectl client version below v1.20:

/etc/containerd# containerd config dump | grep idle
    stream_idle_timeout = "1m"

Additional Information

A Jira- PMK-6283 has been filed to track this issue and the fix will be available in the version: PMK 5.11 release

Last updated