Skip to content

fix(helm): harden default container security context - #6853

Open
WoahitsJoe wants to merge 1 commit into
akuity:mainfrom
WoahitsJoe:fix/helm-default-security-context
Open

fix(helm): harden default container security context#6853
WoahitsJoe wants to merge 1 commit into
akuity:mainfrom
WoahitsJoe:fix/helm-default-security-context

Conversation

@WoahitsJoe

@WoahitsJoe WoahitsJoe commented Aug 21, 2026

Copy link
Copy Markdown

Description

Closes #6852

Hardens the Helm chart's default Kargo container security context by:

  • requiring a non-root user
  • disabling privilege escalation
  • dropping all Linux capabilities
  • applying the runtime default seccomp profile

Component-level securityContext values continue to override the global defaults. This also updates the generated chart documentation and adds a Helm unit test proving that the API container inherits the hardened defaults.

Checklist

Eligibility

  • Linked to an existing issue with no blocking labels (kind/proposal, needs discussion, needs research, maintainer only, area/security, size/large, size/x-large, size/xx-large).
  • Changes documentation only.
  • Changes ten lines or fewer.

Quality

  • Adds or updates corresponding tests.
  • Adds or updates corresponding documentation.

AI Use Disclosure

This PR was written:

  • By a human without AI assistance.
  • By a human with AI assistance. A human has reviewed every line prior to opening the PR.
  • By an AI with human supervision. A human has reviewed every line prior to opening the PR.
  • Entirely by an AI. No human has reviewed this prior to opening the PR.

Sign-Off

All commits:

  • Are signed off by their author (git commit -s) (required)
  • Are cryptographically signed (git commit -S) (encouraged)

Validation

  • make test-chart — 153 tests passed
  • make lint-charts — chart lint passed
  • generated charts/kargo/README.md with the repository's documented generator

Signed-off-by: Joseph <101808325+WoahitsJoe@users.noreply.github.com>
@WoahitsJoe
WoahitsJoe requested a review from a team as a code owner August 21, 2026 08:34
@kargo-governance-bot kargo-governance-bot Bot added needs/area Issue or PR needs to be labeled to indicate what parts of the code base are affected needs/kind Issue or PR needs to be labeled to clarify its nature labels Aug 21, 2026
@netlify

netlify Bot commented Aug 21, 2026

Copy link
Copy Markdown

Deploy Preview for docs-kargo-io ready!

Name Link
🔨 Latest commit efbee19
🔍 Latest deploy log https://app.netlify.com/projects/docs-kargo-io/deploys/6a880d7f1956a40008c89294
😎 Deploy Preview https://deploy-preview-6853.docs.kargo.io
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@kargo-governance-bot kargo-governance-bot Bot added the needs/priority Priority has not yet been determined; a good signal that maintainers aren't fully committed label Aug 21, 2026
@codecov

codecov Bot commented Aug 21, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 31.13%. Comparing base (af85cd1) to head (efbee19).
⚠️ Report is 4 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #6853   +/-   ##
=======================================
  Coverage   31.13%   31.13%           
=======================================
  Files         832      832           
  Lines       81235    81235           
=======================================
  Hits        25294    25294           
  Misses      54470    54470           
  Partials     1471     1471           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@WoahitsJoe WoahitsJoe removed their assignment Aug 23, 2026
@krancour krancour added area/security Has security implications and needs to be handled with great caution kind/proposal Indicates maintainers have not yet committed to a feature request area/chart Affects the Helm chart and removed needs/area Issue or PR needs to be labeled to indicate what parts of the code base are affected labels Aug 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/chart Affects the Helm chart area/security Has security implications and needs to be handled with great caution kind/proposal Indicates maintainers have not yet committed to a feature request needs/kind Issue or PR needs to be labeled to clarify its nature needs/priority Priority has not yet been determined; a good signal that maintainers aren't fully committed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Harden the Helm chart's default container security context

2 participants