<p>We are using actually k8s HA multi master cluster version 1.24 within a <strong>SSL/TLS encrypted, secured and access restricted private network behind a hardware firewall</strong>. Our cluster has <strong>no public endpoints</strong> or any communication to the public internet. We want to disable TLS for the k8s cluster or at least using an insecure way for internal k8s communication. At version &lt; 1.24, there were <strong>--insecure flags</strong> for the kube-apiserver, which has been <strong>removed since 1.24</strong>.</p>
<p>Do version 1.24 provide any alternative for the removed --insecure flags?
How to achieve an insecure communication with 1.24?</p>

DavidL
<p><a href="https://github.com/rancher/cis-operator/issues/158" rel="nofollow noreferrer">Insecure address flags</a> are used to serve unsecured unauthenticated access to the API server. Setting up the apiserver to serve on an insecure port would allow <strong>unauthenticated</strong> and <strong>unencrypted access</strong> to your master node. This would allow attackers who could access this port, to easily take control of this cluster.</p>
<p><a href="https://github.com/kubernetes/kubernetes/blob/master/CHANGELOG/CHANGELOG-1.24.md" rel="nofollow noreferrer">Kubernetes</a> release of 2022(1.24+) aims to make Kubernetes more secure and reliable. In the 1.24 release, there is a single essential change for the kube-scheduler. Insecure flags, such as <code>--address</code> and <code>--port</code>, have been <a href="https://github.com/kubernetes/kubernetes/pull/106865" rel="nofollow noreferrer">removed</a>. It is suggested to use <a href="https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/" rel="nofollow noreferrer"><strong>--bind-address and --secure-port</strong></a> instead. So, there is no alternate option of using an insecure way for internal kubernetes communication.</p>
