Create SLURM container images for Big Bang product team

Slurm Core Components (Slinky Helm chart) Upstream Registry: ghcr.io/slinkyproject Upstream Source: https://github.com/SlinkyProject/slurm-containers

Slurm Operator (Slinky) Upstream Registry: ghcr.io/slinkyproject Upstream Source: https://github.com/SlinkyProject/slurm-operator

Required Images

A. Slurm Operator (Slinky)

• ghcr.io/slinkyproject/slurm-operator:0.3.1
• ghcr.io/slinkyproject/slurm-operator-webhook:0.3.1

Upstream Source: https://github.com/SlinkyProject/slurm-operator

B. Slurm Core Components

• ghcr.io/slinkyproject/slurmctld:25.05-ubuntu24.04
• ghcr.io/slinkyproject/slurmrestd:25.05-ubuntu24.04
• ghcr.io/slinkyproject/slurmdbd:25.05-ubuntu24.04
• ghcr.io/slinkyproject/slurmd:25.05-ubuntu24.04
• ghcr.io/slinkyproject/sackd:25.05-ubuntu24.04 (init/config helper)

Upstream Source: https://github.com/SlinkyProject/containers

Naming Convention

• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurm-operator
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurm-operator-webhook
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurmctld
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurmrestd
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurmdbd
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/slurmd
• registry1.dso.mil/ironbank/opensource/slinkyproject/slurm/sackd

Onboarding Location

• Directory: ironbank/opensource/slinkyproject/slurm for both operator and all core components.

Summary

Request for a new application in Iron Bank.

Tasks

Contributor:

• Add Dockerfile, hardening_manifest.yaml and adhere to Iron Bank requirements
• Ensure container builds successfully in the Iron Bank pipeline
• Provide justifications for findings in the VAT
• Apply the StatusReview label to this issue and wait for feedback

Note: You must mannually apply the StatusReview label in order to have a CHT member review your merge request.

Iron Bank:

• Merge contributor branch to development
• Review findings and justifications
• Merge development to master and close issue

Note: If the above Verification process is rejected for any reason, the Status::Verification label will be removed and the issue will be sent back to Open. Any comments will be listed in this issue for you to address. Once they have been addressed, you must re-add the Status::Verification label.

Questions?

Contact the Iron Bank team by commenting on this issue with your questions or concerns. If you do not receive a response, add /cc @ironbank-notifications/onboarding.

Additionally, Iron Bank hosts an AMA working session every Wednesday from 1630-1730EST to answer questions.

Please read the Iron Bank Documentation for more info