-
Bug
-
Resolution: Done
-
Normal
-
4.12
-
None
-
None
-
1
-
OSDOCS Sprint 229, OSDOCS Sprint 230
-
2
-
False
-
Description of problem:
Creating a loadbalancer Service with loadBalancerSourceRanges attribute is ignored if the OVN provider is enabled on the cluster:
1. with below section on cm/cloud-provider-config in openshift-config namespace:
[LoadBalancer]
lb-provider = ovn
lb-method = SOURCE_IP_PORT
Creating a loadbalancer like below:
---
apiVersion: v1
kind: Service
metadata:
name: udp-lb-sourceranges-svc
namespace: udp-lb-sourceranges-ns
labels:
app: udp-lb-sourceranges-dep
spec:
ports:
- port: 8082
targetPort: 8081
protocol: UDP
selector:
app: udp-lb-sourceranges-dep
type: LoadBalancer
loadBalancerSourceRanges:
- 10.46.22.195/32
results on ignoring the loadBalancerSourceRanges attribute and below log line is shown on openstack-cloud-controller-manager pod inside openshift-cloud-controller-manager namespace:
$ oc logs -n openshift-cloud-controller-manager openstack-cloud-controller-manager-6d744b8c95-thg4q -f [...] W1024 09:34:01.392528 1 loadbalancer.go:1870] LoadBalancerSourceRanges is ignored I1024 09:34:01.643081 1 event.go:294] "Event occurred" object="udp-lb-sourceranges-ns/udp-lb-sourceranges-svc" fieldPath="" kind="Service" apiVersion="v1" type="Normal" reason="EnsuredLoadBalancer" message="Ensured load balancer"
However, it works with Amphora provider.
This bug is for stating this restriction on documentation.
Version-Release number of selected component (if applicable): ocp4.12 release on top of available OSP17.0 (RHOS-17.0-RHEL-9-20220909.n.0).
How reproducible:Always if OVN provider is enabled..