The keycloak namespace only has the ingress policy the Keycloak Operator creates. Neither the Keycloak pod nor the Operator pod has any egress restriction, unlike every other platform namespace. Add a namespace-wide default deny and allow only what is used: DNS, platform-postgres 5432 (server and realm-import jobs), JGroups between Keycloak pods, and for the Operator the API server and the Keycloak management ports. Keycloak ingress stays owned by the Operator policy. Rejected: allowing public 443 like Gitea does. Neither the repository nor the Keycloak CR configures SMTP or an external identity provider, and the only open TCP connections from keycloak-0 on 2026-11-12 were to PostgreSQL. Adding SMTP or an IdP later needs a new egress rule; the README says so. Risk: a missed dependency would break logins for every service. The README lists the post-apply checks (OIDC discovery, a new TCP connection to Postgres from keycloak-0, Operator logs) and the one-line rollback. Verification: render and kubectl diff only add the five policies.
13 lines
213 B
YAML
13 lines
213 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
|
|
namespace: keycloak
|
|
|
|
labels:
|
|
- pairs:
|
|
app.kubernetes.io/part-of: platform
|
|
includeSelectors: false
|
|
|
|
resources:
|
|
- network-policies.yaml
|