veza/k8s/network-policies/chat-server-allow.yaml
senke b103a09a25 chore: consolidate CI, E2E, backend and frontend updates
- CI: workflows updates (cd, ci), remove playwright.yml
- E2E: global-setup, auth/playlists/profile specs
- Remove playwright-report and test-results artifacts from tracking
- Backend: auth, handlers, services, workers, migrations
- Frontend: components, features, vite config
- Add e2e-results.json to gitignore
- Docs: REMEDIATION_PROGRESS, audit archive
- Rust: chat-server, stream-server updates
2026-02-17 16:43:21 +01:00

44 lines
885 B
YAML

# Chat Server: allow ingress from ingress controller, egress to Redis, PostgreSQL, DNS
# WebSocket connections; depends on Redis for pub/sub
---
apiVersion: networking.k8s.io/v1
kind: NetworkPolicy
metadata:
name: chat-server-allow
namespace: veza-production
spec:
podSelector:
matchLabels:
app: veza-chat-server
policyTypes:
- Ingress
- Egress
ingress:
- from:
- namespaceSelector:
matchLabels:
name: ingress-nginx
ports:
- protocol: TCP
port: 8081
- from:
- podSelector: {}
ports:
- protocol: TCP
port: 8081
egress:
- to:
- ipBlock:
cidr: 0.0.0.0/0
ports:
- protocol: TCP
port: 5432
- protocol: TCP
port: 6379
- to:
- namespaceSelector:
matchLabels:
kubernetes.io/metadata.name: kube-system
ports:
- protocol: UDP
port: 53