<p>Is it possible to set the <code>--http2-max-streams-per-connection</code> value for a cluster created by Kops.</p>
<p>I have an interesting situation where one of my nodes falls into a <code>NotReady</code> status whenever I deploy a helm chart to it and I feel like it might be connected to this setting.</p>
<p>The nodes are generally fine and run without any issues, but once I deploy my helm chart, the status of whatever node it gets deployed to changes after a few minutes to <code>NotReady</code> Which I find weird.</p>
<p>I've done a bit of reading and seen a number of similar issues pointing to the setting <code>--http2-max-streams-per-connection</code> but I'm not how to go about setting this.</p>
<p>Any ideas anyone?</p>

Hammed
<p>You should be able to set this by adding the following to the cluster spec:</p>
<pre><code>spec:
  kubeAPIServer:
    http2MaxStreamsPerConnection: &lt;value&gt;
</code></pre>
<p>See <a href="https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#KubeAPIServerConfig" rel="nofollow noreferrer">https://pkg.go.dev/k8s.io/kops/pkg/apis/kops#KubeAPIServerConfig</a> and <a href="https://kops.sigs.k8s.io/cluster_spec/" rel="nofollow noreferrer">https://kops.sigs.k8s.io/cluster_spec/</a></p>
<p>That being said, I do not believe the reason for your <code>NotReady</code> nodes is due to that setting. You may want to join #kops-users on the kubernetes slack space and ask for help triaging that problem.</p>
