Uploaded image for project: 'OpenShift Hosted Control Plane'
  1. OpenShift Hosted Control Plane
  2. HOSTEDCP-1337

Add Kubernetes SCC V2 options to resource's YAML configuration

    XMLWordPrintable

Details

    • 0
    • 0
    • 0

    Description

      Value Statement

      As an ACM admin, I want to add Kubernetes Security Context Constraints (SCC) V2 options to the component's resource YAML configuration to ensure that the Pod runs with the 'readonlyrootfilesystem' and 'privileged' settings, in order to enhance the security and functionality of our application.

      In the resource config YAML, we need to add the follow context:

      securityContext:
        privileged: false
        readOnlyRootFilesystem: true
      

      Affected resources:

      • [x] operator
      • [x] hypershift-addon-agent
      • [x] hypershift-install-job

      Definition of Done for Engineering Story Owner (Checklist)

      • [x] Ensure that the Pod continues to function correctly with the new SCC V2 settings.
      • [ ] Verify that the SCC V2 options are effective in limiting the Pod's privileges and restricting write access to the root filesystem.

      Development Complete

      • The code is complete.
      • Functionality is working.
      • Any required downstream Docker file changes are made.

      Tests Automated

      • [ ] Unit/function tests have been automated and incorporated into the
        build.
      • [ ] 100% automated unit/function test coverage for new or changed APIs.

      Secure Design

      • [ ] Security has been assessed and incorporated into your threat model.

      Multidisciplinary Teams Readiness

      Support Readiness

      • [ ] The must-gather script has been updated.

      Attachments

        Issue Links

          Activity

            People

              rokejungrh Roke Jung
              dbennett@redhat.com Disaiah Bennett
              David Huynh David Huynh
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: