instruction: Create a Dockerfile for security
output: ```dockerfile
  from the underlying
  kernel. This allows for workloads requiring heightened permissions to still be isolated.Additionally, the protection of sandboxed workloads is highly dependent on the method of
  sandboxing. As such, no single recommended profile is recommended for all sandboxed workloads.Items on this page refer to third party products or projects that provide functionality required by Kubernetes. The Kubernetes project authors aren't responsible for those third-party products or projects. See the CNCF website guidelines for more details.You should read the content guide before proposing a change that adds an extra third-party link.FeedbackWas this page helpful?Yes
  NoThanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it on
  Stack Overflow.
  Open an issue in the GitHub Repository if you want to
  report a problem
  or
  suggest an improvement.Last modified February 24, 2025 at 9:31 PM PST: Update pod-security-standards.md (d86a4b409a)  Create child page
   Create an issue
   Print entire sectionProfile DetailsPrivilegedBaselineRestrictedPolicy InstantiationAlternativesPod OS fieldRestricted Pod Security Standard changesUser namespacesFAQWhy isn't there a profile between Privileged and Baseline?What's the difference between a security profile and a security context?What about sandboxed Pods?© 2025 The Kubernetes Authors | Documentation Distributed under CC BY 4.0© 2025 The Linux Foundation ®. ```