Lock Down Container Syscalls With Seccomp Profiles
Run a Deployment under the container runtime's seccomp profile, roll out a custom profile to the worker nodes, and fix a profile that blocks a syscall the application needs.
Tutorials, challenges, courses, skill paths, playgrounds, and more — search the whole library in one place.
Kubernetes enthusiast and certified CKA & CKAD, passionate about building, exploring, and explaining cloud-native technologies. Constantly learning, experimenting, and sharing practical Kubernetes knowledge
Run a Deployment under the container runtime's seccomp profile, roll out a custom profile to the worker nodes, and fix a profile that blocks a syscall the application needs.
The platform team is rolling out Pod Security Admission. A monitoring agent is already blocked, the storefront team needs a staged rollout, and payments must move to the strictest level without losing its running service.
The security team left five NetworkPolicy files on the workstation. Only one of them lets the frontend reach the backend while granting nothing more. Identify it and deploy it, unchanged.
A Snake game Deployment and ClusterIP Service are already running in the snake namespace. Create a Traefik Ingress that serves the game over HTTPS using an existing cert-manager-issued TLS Secret.