Bug 1769015
| Summary: | Missing openapi CRD definitions for oc explain to work | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Maciej Szulik <maszulik> | |
| Component: | Networking | Assignee: | Aniket Bhat <anbhat> | |
| Networking sub component: | openshift-sdn | QA Contact: | zhaozhanqi <zzhao> | |
| Status: | CLOSED ERRATA | Docs Contact: | ||
| Severity: | medium | |||
| Priority: | medium | CC: | anbhat, bbennett, huirwang, nagrawal, weliang | |
| Version: | 4.3.0 | |||
| Target Milestone: | --- | |||
| Target Release: | 4.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 1782303 (view as bug list) | Environment: | ||
| Last Closed: | 2020-05-13 21:52:17 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: | ||||
| Bug Blocks: | 1777707, 1782303, 1798142 | |||
|
Description
Maciej Szulik
2019-11-05 18:27:46 UTC
*** Bug 1777707 has been marked as a duplicate of this bug. *** Verification failed on 4.4.0-0.nightly-2020-01-24-141203 which description is still empty.
[root@dhcp-41-193 FILE]# oc explain clusternetwork
KIND: ClusterNetwork
VERSION: network.openshift.io/v1
DESCRIPTION:
<empty>
Tested and verified on openshift-sdn using 4.4.0-0.nightly-2020-01-30-123556:
[root@dhcp-41-193 FILE]# oc explain clusternetwork
KIND: ClusterNetwork
VERSION: network.openshift.io/v1
DESCRIPTION:
ClusterNetwork describes the cluster network. There is normally only one
object of this type, named "default", which is created by the SDN network
plugin based on the master configuration when the cluster is brought up for
the first time.
FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an
object. Servers should convert recognized schemas to the latest internal
value, and may reject unrecognized values. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
clusterNetworks <[]Object> -required-
ClusterNetworks is a list of ClusterNetwork objects that defines the global
overlay network's L3 space by specifying a set of CIDR and netmasks that
the SDN can allocate addresses from.
hostsubnetlength <integer>
HostSubnetLength is the number of bits of network to allocate to each node.
eg, 8 would mean that each node would have a /24 slice of the overlay
network for its pods
kind <string>
Kind is a string value representing the REST resource this object
represents. Servers may infer this from the endpoint the client submits
requests to. Cannot be updated. In CamelCase. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
metadata <Object>
Standard object's metadata. More info:
https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
mtu <integer>
MTU is the MTU for the overlay network. This should be 50 less than the MTU
of the network connecting the nodes. It is normally autodetected by the
cluster network operator.
network <string>
Network is a CIDR string specifying the global overlay network's L3 space
pluginName <string>
PluginName is the name of the network plugin being used
serviceNetwork <string> -required-
ServiceNetwork is the CIDR range that Service IP addresses are allocated
from
vxlanPort <integer>
VXLANPort sets the VXLAN destination port used by the cluster. It is set by
the master configuration file on startup and cannot be edited manually.
Valid values for VXLANPort are integers 1-65535 inclusive and if unset
defaults to 4789. Changing VXLANPort allows users to resolve issues between
openshift SDN and other software trying to use the same VXLAN destination
port.
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:0581 |