OpenShiftSDN: introduce OVS anti-selector - #346
Conversation
openshift-ci-robot
added
do-not-merge/work-in-progress
If you file a corresponding PR for OVN, I'd merge it. Note that you'll have to adjust some bindmounts as well. |
PR for ovn: #357 |
|
Documented in PR 375 |
OpenShiftSDN is shipped with its own openvswitch service running as a separate daemonset. However, in some cases we may want to use an external openvswitch running on the host (e.g. to use it for host networking). In order to support a mixed environment where some hosts have this external service and some don't, we introduce openvswitch anti-selector: network.operator.openshift.io/external-openvswitch Note that this selector has to be set *before* the operator is started. Otherwise, the label would not take effect on already scheduled pods. Signed-off-by: Petr Horacek <phoracek@redhat.com>
0c9b2a8 to
55cf4a7
Compare
phoracek
changed the title
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: phoracek, squeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
|
@phoracek: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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/test-infra repository. I understand the commands that are listed here. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
6 participants
OpenShiftSDN is shipped with its own openvswitch service running
as a separate daemonset. However, in some cases we may want to use
an external openvswitch running on the host (e.g. to use it for
host networking). In order to support a mixed environment where some
hosts have this external service and some don't, we introduce
openvswitch anti-selector:
network.operator.openshift.io/external-openvswitchNote that this selector has to be set before the operator is started.
Otherwise, the label would not take effect on already scheduled
pods.
TODO: documentation
Signed-off-by: Petr Horacek phoracek@redhat.com