Securing pod and containers is an important aspect of protecting your Kubernetes environment. Among other things, pods and containers are individual units of computation that finally bowed hostility techniques that can be used as part of an attack on your Kubernetes group.
Since the pod is also the smallest of resources you can deploy and manage in Kubernetes, apply security at this level ensures a greater fine-grained control scoped to the individual application components. You can know about Kubernetes security through kubevious.io.
Context Kubernetes Security
The starting point for understanding the workings of the security pod in Kubernetes is what is known as the "security context," which references the specific constraints to access and privileges on the level of the individual pods are configured at runtime.
Pod level Security Context
The purpose of this constraint is several-fold, namely to limit the vulnerability of each pod is given to compromise by attackers techniques as described in the Kubernetes matrix attack and to limit the blast radius of any potential attack outside the set of containers.
To define the settings for a given pod, Security Context fields should be included in the manifest pod; Pod Security Context this reference object that stores security attributes that are relevant to the use of API Kubernetes.
Container Security Context level
Pod-level security context will generate constraints that are applied to all containers that run within the relevant pod. But you may not always want the same arrangement applies to all containers in a given pod, so Kubernetes also allows you to specify the security context for individual containers as well.
Security Kubernetes Policy
Now that we have discussed the concept of the security context in Kubernetes, which provides the ability to declare the security parameters for the pods and containers are applied at runtime, we will explore the complementary features in Kubernetes which further enforce this setting.