Kubernetes scheduler code should support setting a SecurityContext

Description

Contributor guide

Tech stack

javakubernetes

Domain

backendinfrastructuresecurity

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

Kubernetes basicsJava

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Examine the Heron scheduler code for Kubernetes, specifically the StatefulSet and Pod creation logic. Look for places where SecurityContext is not set but could be added, likely in the Kubernetes controller or submission code. Check existing tests and the Kubernetes client library used (e.g., fabric8). The issue can be resolved by adding a SecurityContext field to the relevant data structures and passing it through to the Kubernetes API calls. Consult the Kubernetes documentation for SecurityContext and PodSecurityPolicy.