Kubernetes - Set the security context for a Pod

  To specify security settings for a Pod, include the securityContext field in the Pod specification. The securityContext field is a PodSecurityContext object. The security settings that you specify for a Pod apply to all Containers in the Pod. Here is a configuration file for a Pod that has a securityContext and an emptyDir volume:

Without Security Context :

apiVersion: apps/v1

kind: Deployment

metadata:

  name: busybox-nosc

  namespace: demo

spec:

  replicas: 1

  selector:

   matchLabels:

     test: app

  template:

    metadata:

      labels:

        test: app

    spec:

     containers:

     - name: busybox-con

       image: busybox

       args:

       - /bin/sh

       - -c

       - touch /tmp/healthy; sleep 60; rm -rf /tmp/healthy; sleep 600

       volumeMounts:

       - name: sec-volume

         mountPath: /data/demo

     volumes:

     - name: sec-volume

       emptyDir: {}


Security Context on Pod level


kind: Deployment

metadata:

  name: busybox-nosc

  namespace: demo

spec:

  replicas: 1

  selector:

   matchLabels:

     test: app

  template:

    metadata:

      labels:

        test: app

    spec:

     containers:

     - name: busybox-con

       image: busybox

       args:

       - /bin/sh

       - -c

       - touch /tmp/healthy; sleep 60; rm -rf /tmp/healthy; sleep 600

       volumeMounts:

       - name: sec-volume

         mountPath: /data/demo

     volumes:

     - name: sec-volume

       emptyDir: {}

     securityContext:

       runAsUser: 1000

       runAsGroup: 3000

       fsGroup: 2000


Security Context on container level


kind: Deployment
metadata:
  name: busybox-nosc
  namespace: demo
spec:
  replicas: 1
  selector:
   matchLabels:
     test: app
  template:
    metadata:
      labels:
        test: app
    spec:
     containers:
     - name: busybox-con
       image: busybox
       args:
       - /bin/sh
       - -c
       - touch /tmp/healthy; sleep 60; rm -rf /tmp/healthy; sleep 600
       volumeMounts:
       - name: sec-volume
         mountPath: /data/demo
       securityContext:
         runAsUser: 5000
         runAsGroup: 6000

     volumes:
     - name: sec-volume
       emptyDir: {}
     securityContext:
       runAsUser: 1000
       runAsGroup: 3000
       fsGroup: 2000

Comments

Post a Comment

Popular posts from this blog

Terraform

Image
  Terraform is an infrastructure as code tool that lets you build, change, and version cloud and on-prem resources safely and efficiently. HashiCorp Terraform is an infrastructure as code tool that lets you define both cloud and on-prem resources in human-readable configuration files that you can version, reuse, and share. You can then use a consistent workflow to provision and manage all of your infrastructure throughout its lifecycle. Terraform can manage low-level components like compute, storage, and networking resources, as well as high-level components like DNS entries and SaaS features. How does Terraform work? Terraform creates and manages resources on cloud platforms and other services through their application programming interfaces (APIs). Providers enable Terraform to work with virtually any platform or service with an accessible API. HashiCorp and the Terraform community have already written  thousands of providers  to manage many different types of resources...
Read more

Different Types of Reports in Scrum - Agile

Image
  Introduction to Agile Reporting I’m not going to elaborate on the Agile Framework itself here.  1. Sprint Burndown At a Sprint-level, the burndown presents the  easiest way to track and report status  (the proverbial  Red / Amber / Green ), i.e., whether your Sprint is on or off-track, and what are the chances of meeting the Sprint goals. The burndown chart – when used right – can provide  near-real time updates  on Sprint progress. “If your team do it right, then they would take in just the right amount of work into a sprint.” At the beginning of a Sprint, the Scrum team perform Sprint Planning and agree to take on development work worth a certain number of Story points. This forms the basis for the Sprint Burndown chart. The total story points agreed at the beginning of the sprint make up the y-axis, and the individual dates in the Sprint make up x-axis. If your team do it right, then they would take in just the right amount of work into ...
Read more

Scrum Master Interview help - Bootcamp

Understanding the MoSCoW prioritization | How to implement it into your project Projects, irrespective of their size or complexity, often juggle numerous tasks and requirements. In such a scenario,  MoSCoW prioritization  becomes essential to ensure the successful completion of the project.  Besides, it is also a very effective way to manage project priorities. With a straightforward and adaptable approach, the MoSCoW method helps manage stakeholder expectations and improve project outcomes. What is the MoSCoW prioritization technique?  The MoSCoW method is a prioritization matrix widely used in project management and software development. The term MoSCoW is an acronym that stands for  Must have ,  Should have ,  Could have , and  Won’t have , each denoting a level of priority. Here is the breakdown of the MoSCoW method:  Must have:  These are critical requirements that the project cannot be completed withou...
Read more