-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.18.0
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
No
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When enabled BGP feature, and create egressip with only one worker. egressip cannot be assigned to the worker
Version-Release number of selected component (if applicable):
using latest cluster-bot build: build 4.18,openshift/cluster-network-operator#2442,openshift/ovn-kubernetes#2239
4.18.0-0.test-2024-11-28-094148-ci-ln-1k98rjk-latest
How reproducible:
Steps to Reproduce:
1. setup cluster and enable BGP
2. Create egressip and assign one worker
apiVersion: k8s.ovn.org/v1
kind: EgressIP
metadata:
name: egress-group1
spec:
egressIPs:
- 11.131.100.100
podSelector:
matchLabels:
name: test-pods
namespaceSelector:
matchLabels:
env: prod
3. oc label node worker-2 k8s.ovn.org/egress-assignable=""
4. check egressip and found it canot be assigned to worker-2
- oc get egressip
NAME EGRESSIPS ASSIGNED NODE ASSIGNED EGRESSIPS
egress-group1 11.131.100.100
Actual results:
Expected results:
egressip can be assigned to worker-2
Additional info: