Summary

Containerized workloads allow administrators to add capabilities quickly and easily to a system, while retaining possible dependencies within a container. Each container hosts its own dependencies, allowing containers to be removed and added from the system without affecting others. With SELinux, this workload is further isolated from the host and, in case of sVirt protections, also from each other.

We've seen how systemd has container support but lacks sVirt-based protections, and how podman can apply sVirt protections on its own container environments. We learned that Docker and podman are very similar in usage, yet different under the hood. Both frameworks allow us to apply different SELinux types to the containers and resources, and with udica we've learned how to create custom policies without much development effort. Finally, we've seen how Kubernetes can be configured to use SELinux labeling as well.

With all these SELinux-capable technologies behind...