Add ceph-csi NetworkPolicy manifest and CI deployment - #6374
Conversation
c9e8b0b to
b0d6472
Compare
Add deploy/ceph-csi-networkpolicy.yaml with ingress policies for CephFS and RBD CSI plugins. Apply it automatically during rook.sh cluster setup and teardown. Expose standalone deploy/teardown commands in rook.sh and minikube.sh. Target namespace is configurable via CEPHCSI_NAMESPACE (default: "default"). Signed-off-by: Oded Viner <oviner@redhat.com>
b0d6472 to
27a7db7
Compare
|
/test ci/centos/mini-e2e-operator/k8s-1.36 |
By leaving a comment like that, you can trigger the CI job. Note that the command needs to be the only line in the comment, without spaces/linebreaks/... |
Hey @nixpanic , is there a recommended way to verify that I’ve applied the NetworkPolicy to the correct namespace for the CSI pods? Looking at this line in the PR: https://github.com/ceph/ceph-csi/pull/6374/changes#diff-709a4aacc8147bf2f677d2dd2a694c1bba9716a5aca85ead45c53ad3f18ee872R16 |
|
Isnt this change required in ceph-csi-operator rather than here? |
|
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions. |
3 participants
This PR is just a prototype for exploration and will be closed shortly.
This PR is just a prototype for exploration and will be closed shortly."
Add deploy/ceph-csi-networkpolicy.yaml with ingress policies for CephFS and RBD CSI plugins. Apply it
automatically during rook.sh cluster setup and
teardown. Expose standalone deploy/teardown commands in rook.sh and minikube.sh. Target namespace is
configurable via CEPHCSI_NAMESPACE (default: "default").
Describe what this PR does
Provide some context for the reviewer
Is there anything that requires special attention
Do you have any questions?
Is the change backward compatible?
Are there concerns around backward compatibility?
Provide any external context for the change, if any.
For example:
Related issues
Mention any github issues relevant to this PR. Adding below line
will help to auto close the issue once the PR is merged.
Fixes: #issue_number
Future concerns
List items that are not part of the PR and do not impact it's
functionality, but are work items that can be taken up subsequently.
Checklist:
guidelines in the developer
guide.
Request
notes
updated with breaking and/or notable changes for the next major release.
Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:
/retest ci/centos/<job-name>: retest the<job-name>after unrelatedfailure (please report the failure too!)