Description of problem:
There is no description for PodNetworkConnectivityCheck CRD reported by `oc explain`.
Steps to Reproduce:
`oc explain PodNetworkConnectivityCheck`
A description of what this CRD is for.
Verified in latest 4.6.0-0.nightly-2020-09-22-073212, still reproduced. Waiting for bumping PR for the merged dependent https://github.com/openshift/api/pull/741
The api change needs revendoring into kube-apiserver-operator.
Moving out of 4.6. This is cosmetics and can be backported later.
The CRD is opt-in now and unsupported. So low prio.
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.8.0-0.nightly-2021-06-09-142759 True False 9h Cluster version is 4.8.0-0.nightly-2021-06-09-142759
$ oc explain PodNetworkConnectivityCheck
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:
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:
Standard object's metadata. More info:
spec <Object> -required-
Spec defines the source and target of the connectivity check
Status contains the observed status of the connectivity check
From Comment #7, the DESCRIPTION for PodNetworkConnectivityCheck is terrible，it's the equivalent of nothing being explained. Let's see a normal description, as below,
$ oc explain crd
CustomResourceDefinition represents a resource that should be exposed on
the API server. Its name MUST be in the format <.spec.name>.<.spec.group>.
I think the linked PR doesn't fixed the bug, I have to move it ASSIGNED.