Allow access to the private network for cloud and firewall controller

On a on-premise setup of garden cluster, the endpoints lie in a private network.
metal-stack · Jan 30, 2024 · 1beff8e · 1beff8e
1 parent 88093b7
commit 1beff8e
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 0 deletions.
diff --git a/charts/internal/control-plane/templates/cloud-controller-manager.yaml b/charts/internal/control-plane/templates/cloud-controller-manager.yaml
@@ -47,6 +47,7 @@ spec:
         networking.gardener.cloud/from-prometheus: allowed
         networking.gardener.cloud/to-dns: allowed
         networking.gardener.cloud/to-shoot-apiserver: allowed
+        networking.gardener.cloud/to-private-networks: "allowed"
         networking.gardener.cloud/to-public-networks: allowed
         networking.resources.gardener.cloud/to-kube-apiserver-tcp-443: "allowed"
     spec:

diff --git a/charts/internal/control-plane/templates/firewall-controller-manager.yaml b/charts/internal/control-plane/templates/firewall-controller-manager.yaml
@@ -102,6 +102,7 @@ spec:
         networking.gardener.cloud/from-prometheus: "allowed"
         networking.gardener.cloud/to-dns: "allowed"
         networking.gardener.cloud/to-public-networks: "allowed"
+        networking.gardener.cloud/to-private-networks: "allowed"
         networking.gardener.cloud/to-shoot-apiserver: "allowed"
         networking.gardener.cloud/to-runtime-apiserver: "allowed"
         networking.resources.gardener.cloud/to-kube-apiserver-tcp-443: "allowed"