IR-523: setting read only root filesystem #1198
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@ricardomaraschini: This pull request references IR-455 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 epic to target the "4.19.0" version, but no target version was set. In response to this:
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-ci
bot
added
the
do-not-merge/work-in-progress
|
Skipping CI for Draft Pull Request. |
|
/test all |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ricardomaraschini The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci
bot
added
the
approved
ricardomaraschini
force-pushed
the
read-only-root-fs
branch
from
a431f11 to
66aa3d2
Compare
|
/retest |
ricardomaraschini
force-pushed
the
read-only-root-fs
branch
from
66aa3d2 to
830b484
Compare
|
/retest |
ricardomaraschini
force-pushed
the
read-only-root-fs
branch
from
830b484 to
86430b3
Compare
|
/retest |
set the root filesystem as readonly for: - the operator deployment. - the nodeca daemonset. - the image registry deployment. - the pruner cronjob. the operator requires access to /tmp so this directory is not mounted out of an `emptyDir`.
ricardomaraschini
force-pushed
the
read-only-root-fs
branch
from
86430b3 to
2ba9c4a
Compare
ricardomaraschini
changed the title
|
@ricardomaraschini: This pull request references IR-523 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 story to target the "4.19.0" version, but no target version was set. In response to this:
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. |
|
/jira refresh |
|
@ricardomaraschini: This pull request references IR-523 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 story to target the "4.19.0" version, but no target version was set. In response to this:
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-ci
bot
removed
the
do-not-merge/work-in-progress
|
/jira refresh |
|
@ricardomaraschini: This pull request references IR-523 which is a valid jira issue. In response to this:
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. |
|
/retest |
|
@ricardomaraschini: The following tests failed, say
Full PR test history. Your PR dashboard. 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. |
|
I am closing this one in order to avoid confusion. This was just an attempt at addressing the issue. |
set the root filesystem as readonly for: