Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update init containers to be PSS compliant in the apps namespace #2620

Merged
merged 1 commit into from
Oct 4, 2024

Conversation

nimalank7
Copy link
Contributor

@nimalank7 nimalank7 commented Sep 27, 2024

Description:

  • Enforce initContainers in the app namespace to be compliant when PSS is set to restricted
  • Tested in integration and observed that content-data-admin initContainers were starting properly
  • govuk-mirror-sync-cronjob can't be tested in integration as this has no mirrors so the PR will have to be merged and we will have to manually inspect staging ot see if it succeeds.
  • As part of Roll out PSS Restricted profile. #1883
  • Paired with @MahmudH

@nimalank7 nimalank7 force-pushed the update-init-containers-PSS-compliant branch 3 times, most recently from c012fe1 to f124433 Compare October 2, 2024 15:56
@nimalank7 nimalank7 changed the title Update init containers to be PSS compliant Update init containers to be PSS compliant in the apps namespace Oct 2, 2024
@nimalank7 nimalank7 force-pushed the update-init-containers-PSS-compliant branch from f124433 to be33f41 Compare October 3, 2024 08:59
@nimalank7 nimalank7 marked this pull request as ready for review October 3, 2024 09:00
@MahmudH MahmudH requested a review from a team October 3, 2024 09:12
capabilities:
drop: ["ALL"]
drop: {{ .Values.securityContext.capabilities.drop }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need to read these in as Values?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No particular reason. Mostly just being consistent with extracting everything out to values.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're not changing it (and we wanna actually enforce this value anyway) - there's no need to have it as a variable. Just adds complexity to the configuration.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yep that's fair. I've pushed up now!

Description:
- Enforce initContainers in the `app` namespace to be compliant when PSS is set to [restricted](https://kubernetes.io/docs/concepts/security/pod-security-standards/)
- Tested in integration and observed that `content-data-admin` initContainers were starting properly
- `govuk-mirror-sync-cronjob` can't be tested in integration as this has no mirrors so the PR will have to be merged and we will have to manually inspect staging ot see if it succeeds.
- As part of #1883
- Paired with @MahmudH
@nimalank7 nimalank7 force-pushed the update-init-containers-PSS-compliant branch from be33f41 to 6eb6ac4 Compare October 4, 2024 10:00
@nimalank7 nimalank7 merged commit d42e649 into main Oct 4, 2024
4 checks passed
@nimalank7 nimalank7 deleted the update-init-containers-PSS-compliant branch October 4, 2024 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants