Description of problem:
In nextgen env, Use `oc explain dc` met error: Couldn't find resource for "apps.openshift.io/v1, Kind=DeploymentConfig"
The same like : bc , scc , project and so on.
Ansible-installed BRYO env doesn't have the issue.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Login openshift,and create project;
2. Use command : `oc explain dc`
2. Met error: Couldn't find resource for "apps.openshift.io/v1, Kind=DeploymentConfig"
2. Should works well
'explain' doesn't currently work for custom resources like many 4.0 configuration types. There's work upstream to address this [1,2,3].
Additionally, there is a PR open  to address openshift-specific types.
Origin PR  has merged.
Confirmed with latest version, the issue has fixed:
[root@dhcp-140-138 ~]# oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.0.0-0.alpha-2019-02-11-201342 True False 5m10s Cluster version is 4.0.0-0.alpha-2019-02-11-201342
[root@dhcp-140-138 ~]# oc explain dc
Deployment Configs define the template for a pod and manages deploying new
images or configuration changes. A single deployment configuration is
usually analogous to a single micro-service. Can support many different
deployment patterns, including full restart, customizable rolling updates,
and fully custom behaviors, as well as pre- and post- deployment hooks.
Each individual deployment is represented as a replication controller. A
deployment is "triggered" when its configuration is changed or a tag in an
Image Stream is changed. Triggers can be disabled to allow manual control
over a deployment. The "strategy" determines how the deployment is carried
out and may be changed at any time. The `latestVersion` field is updated
when a new deployment is triggered by any means.
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.
spec <Object> -required-
Spec represents a desired deployment state and how to deploy to it.
Status represents the current deployment state.
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.