You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit adds the support to enable host network in the Kubewarden
stack. This is done by enabling a CLI flag in the controller. Once this
is done, all the policy server deployments are configured to use host
network as well.
Furthermore, to allow user to fix port conflicts issues, 3 new fields
have been added to the policy server spec. This fields allow users to
define the ports to be used by the policy server deployment.
Assisted-by: Github Copilot
Signed-off-by: José Guilherme Vanz <jguilhermevanz@suse.com>
refactor(webhook): remove metricsPort conflict validation
spec.metricsPort only controls the metrics Service Port (the externally
visible scrape port) and has no effect on pod-side ports. Since it
operates at a different layer than webhookPort and readinessProbePort,
there is no meaningful conflict to validate against. The only pod-side
conflict check that remains is webhookPort vs readinessProbePort.
As a consequence, the defaultMetricsPort parameter is removed from
SetupWebhookWithManager and the policyServerValidator struct, simplifying
the webhook setup chain in main.go.
Assisted-by: Github Copilot
Signed-off-by: José Guilherme Vanz <jguilhermevanz@suse.com>
Copy file name to clipboardExpand all lines: charts/kubewarden-controller/templates/NOTES.txt
+8Lines changed: 8 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -11,3 +11,11 @@ If you'd like to support us, we'd love to hear from you as one of our adopters.
11
11
Adopters can be public or private.
12
12
13
13
Learn how to add your organization as a Kubewarden adopter by checking out the ADOPTERS.md file here: https://github.com/kubewarden/community/blob/main/ADOPTERS.md
14
+
15
+
{{ if .Values.hostNetwork }}
16
+
⚠️ WARNING ⚠️
17
+
Host Network is enabled. Ensure you set appropriate podAntiAffinity rules to prevent host port conflicts between controller replicas on the same node.
18
+
{{ if eq .Values.telemetry.mode "sidecar" }}
19
+
Telemetry sidecar mode (telemetry.mode=sidecar) is incompatible with host network. This chart rejects that configuration and rendering/installation will fail when hostNetwork=true and telemetry.mode=sidecar. Use telemetry.mode=custom with a remote collector instead, or disable hostNetwork.
{{- fail "hostNetwork and telemetry.mode=sidecar are incompatible: OpenTelemetry sidecar injection causes port conflicts in host-network mode. Use telemetry.mode=custom with a remote collector instead." -}}
0 commit comments