chore(langfuse): set pod security standards

This commit is contained in:
Masaki Yatsu
2025-12-01 17:22:00 +09:00
parent 05f8489d3d
commit d02701d5c1
3 changed files with 43 additions and 2 deletions

View File

@@ -325,6 +325,7 @@ Key configuration files:
## Security Considerations
- **Pod Security Standards**: Namespace configured with **restricted** enforcement
- **Secrets Management**: All credentials stored in Vault and synced via External Secrets Operator
- **OIDC Authentication**: No local password storage, authentication delegated to Keycloak
- **API Key Security**: Keys are hashed and stored securely in PostgreSQL
@@ -332,6 +333,20 @@ Key configuration files:
- **Network Isolation**: Internal services communicate via cluster network
- **Database Credentials**: Unique user per application with minimal privileges
### Pod Security Standards
The Langfuse namespace is configured with **restricted** Pod Security Standards:
- `pod-security.kubernetes.io/enforce=restricted`
- `pod-security.kubernetes.io/warn=restricted`
All pods (Langfuse web, worker, and Valkey) run with restricted-compliant security contexts:
- `runAsNonRoot: true` - Prevents containers from running as root
- `allowPrivilegeEscalation: false` - Blocks privilege escalation
- `seccompProfile.type: RuntimeDefault` - Enables seccomp filtering
- `capabilities.drop: [ALL]` - Drops all Linux capabilities
## References
- [Langfuse Documentation](https://langfuse.com/docs)