Bug 1823400

Summary: Allow to only enable hybrid overlay without specifying Windows networks CIDRs
Product: OpenShift Container Platform Reporter: Ricardo Carrillo Cruz <ricarril>
Component: NetworkingAssignee: Jacob Tanenbaum <jtanenba>
Networking sub component: ovn-kubernetes QA Contact: zhaozhanqi <zzhao>
Status: CLOSED ERRATA Docs Contact:
Severity: high    
Priority: unspecified CC: anusaxen, jtanenba, zzhao
Version: 4.5Keywords: UpcomingSprint
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1823399 Environment:
Last Closed: 2020-07-13 17:27:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1823399    

Description Ricardo Carrillo Cruz 2020-04-13 15:21:59 UTC
The Hybrid Overlay feature allows to connect to external Windows networks.
For that, a config needs to be added to networks.operator.openshift.io similar to this:

spec:
  defaultNetwork:
    type: OVNKubernetes
    ovnKubernetesConfig:
      hybridOverlayConfig:
        hybridClusterNetwork:
        - cidr: 10.132.0.0/14
          hostPrefix: 23

However OVN Kubernetes already has that CIDR has default value, thus there's no point to forcing user to specify that.
Moreover, on the hybrid overlay external GW work that is been developed we want to leverage the VXLAN tunnels created by hybrid overlay but we don't care about Windows networks.

Comment 1 Anurag saxena 2020-04-13 18:51:10 UTC
Looks good to me on 4.5.0-0.nightly-2020-04-13-133703
# oc patch network.operator cluster --type=merge -p '{"spec":{"defaultNetwork":{"ovnKubernetesConfig":{"hybridOverlayConfig":{}}}}}'

Network operator reconcile this change successfully and restarts pods under openshift-ovn-kubernetes project to reflect the same

Comment 5 errata-xmlrpc 2020-07-13 17:27:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409