Repository navigation
fix(deploy): set runAsNonRoot on the portal Job and CronJob containers - #629
Conversation
The cluster's pod-security policy reads runAsNonRoot per container and does not fall back to the pod-level setting, so it refused the portal migration Job and blocked every business-site deploy. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Checked against the live policy, The rejection comes from its per-container rule. For every container, init and ephemeral included, it requires:
At Production impact: |
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining
|
Heads-up for this PR's owner: #630 makes the same two container-level |
@codex review |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Codex Review: Didn't find any major issues. What shall we delve into next? Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Readiness at
|

Why
The site has stopped deploying: since the latest release, the cluster refuses the portal's schema migration job because its security setting is declared only for the whole pod, while the cluster's rule checks each container. Until this lands, no business-site release reaches production.
What
The portal's migration job and its daily retention job now state the non-root setting on their container too, so the cluster accepts them and deploys resume. Nothing else about the jobs changes.
No issue: trivial fix.