Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1823399

Summary: Allow to only enable hybrid overlay without specifying Windows networks CIDRs
Product: OpenShift Container Platform Reporter: Ricardo Carrillo Cruz <ricarril>
Component: NetworkingAssignee: Ricardo Carrillo Cruz <ricarril>
Networking sub component: ovn-kubernetes QA Contact: Anurag saxena <anusaxen>
Status: CLOSED ERRATA Docs Contact:
Severity: medium    
Priority: high CC: anusaxen, bbennett, rkhan, zzhao
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1823400 (view as bug list) Environment:
Last Closed: 2020-05-26 16:50:32 UTC Type: Bug
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: 1823400    
Bug Blocks:    
Attachments:
Description Flags
oc describe on ovnkube-master none

Description Ricardo Carrillo Cruz 2020-04-13 15:13:17 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 5 Anurag saxena 2020-04-15 18:31:23 UTC
Created attachment 1679153 [details]
oc describe on ovnkube-master

Comment 12 errata-xmlrpc 2020-05-26 16:50:32 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:2180