feat: bump kube-service-exposer to v0.2.0

Contains the fix for the goroutine leak on port conflict, see: https://github.com/siderolabs/kube-service-exposer/releases/tag/v0.2.0 Also, use the new `--disallowed-host-port-ranges` flag to prevent a set of known ports used by Talos to not be used by the exposer. Signed-off-by: Utku Ozdemir <utku.ozdemir@siderolabs.com>
siderolabs · Aug 15, 2024 · 1cb1080 · 1cb1080
1 parent dd510e9
commit 1cb1080
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/...al/backend/runtime/omni/controllers/omni/data/kube-service-exposer-config-patch.tmpl.yaml b/...al/backend/runtime/omni/controllers/omni/data/kube-service-exposer-config-patch.tmpl.yaml
@@ -52,9 +52,10 @@ cluster:
                 - operator: Exists
               containers:
                 - name: omni-kube-service-exposer
-                  image: ghcr.io/siderolabs/kube-service-exposer:v0.1.4
+                  image: ghcr.io/siderolabs/kube-service-exposer:v0.2.0
                   args:
                     - --debug=false
                     - --annotation-key={{ .AnnotationKey }}
                     # siderolink CIDR
                     - --bind-cidrs="fdae:41e4:649b:9303::/64"
+                    - --disallowed-host-port-ranges=6443,10250,50000-50001