OTA-2111: set readOnlyRootFilesystem on console plugin container

[jrangelramos]

Summary

• Adds readOnlyRootFilesystem: true to the console plugin container's securityContext
• Mounts emptyDir volumes for /tmp, /var/cache/nginx, and /run — the paths nginx needs at runtime
• Aligns with existing hardening in the CVO deployment and bootstrap pod, which already set this field

References

• Jira: https://redhat.atlassian.net/browse/OTA-2111

Test plan

• YAML validates without errors
• Volume names match between volumeMounts and volumes
• All 1114 unit tests pass (make test)
• Deploy to a test cluster and verify the console plugin pod starts and serves correctly

🤖 Generated with Claude Code

[openshift-ci-robot]

@jrangelramos: This pull request references OTA-2111 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the weakness to target the "5.1.0" version, but no target version was set.

Details

In response to this:

Summary

• Adds readOnlyRootFilesystem: true to the console plugin container's securityContext
• Mounts emptyDir volumes for /tmp, /var/cache/nginx, and /run — the paths nginx needs at runtime
• Aligns with existing hardening in the CVO deployment and bootstrap pod, which already set this field

References

• Jira: https://redhat.atlassian.net/browse/OTA-2111

Test plan

• YAML validates without errors
• Volume names match between volumeMounts and volumes
• All 1114 unit tests pass (make test)
• Deploy to a test cluster and verify the console plugin pod starts and serves correctly

🤖 Generated with Claude Code

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-merge-bot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: LGTM mode

[coderabbitai]

Warning

Review limit reached

@jrangelramos, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 51 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: 56097c20-648f-4f63-b192-47c363285a23

📥 Commits

Reviewing files that changed from the base of the PR and between 208b01a and 2a9c1f2.

📒 Files selected for processing (1)

• pkg/agenticrun/bindata/assets/deployment.yaml

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jrangelramos
Once this PR has been reviewed and has the lgtm label, please assign davidhurta for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@jrangelramos: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.