fix(thelounge): allow ingress from cilium gateway entity
Security Scan / Checkov PR Review (push) Has been skipped
Validate Manifests / Kubernetes Schema Validation (push) Successful in 6s
Best Practices / Polaris PR Review (push) Has been skipped
Best Practices / Resource Usage Analysis (push) Successful in 6s
Validate Manifests / Kustomize Build Test (push) Successful in 4s
Security Scan / Trivy PR Review (push) Has been skipped
Best Practices / Kube-score Analysis (push) Failing after 7s
Security Scan / Trivy Security Scan (push) Successful in 7s
Best Practices / Polaris Audit (push) Failing after 8s
Best Practices / PR Summary Report (push) Has been skipped
Validate Manifests / YAML Lint (push) Failing after 4s
Security Scan / Checkov IaC Scan (push) Failing after 30s

The previous selector matched an Istio-style label that does not exist
on Cilium gateway pods, which caused default-deny ingress and blocked
access to thelounge. Use fromEntities: ingress to match Cilium's own
gateway/ingress pods, consistent with the cluster repo's webhook CNP.
This commit is contained in:
2026-05-21 10:15:19 -04:00
parent 19b175dcf2
commit 2308e1103a
+1 -8
View File
@@ -8,15 +8,8 @@ spec:
matchLabels:
app.kubernetes.io/name: thelounge
ingress:
- fromEndpoints:
- matchLabels:
k8s:io.kubernetes.pod.namespace: gateway-system
k8s:gateway.networking.k8s.io/gateway-name: external
toPorts:
- ports:
- port: "9000"
protocol: TCP
- fromEntities:
- ingress
- host
toPorts:
- ports: