-
Notifications
You must be signed in to change notification settings - Fork 4.7k
[regression] oc explain doesn't work #17872
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I tried to use older versions but it didn't work too, that surprised me. I tried to remove |
Is this different than #17766 ? When you run as a cluster-admin does it work or fail? |
Opened #17874 for permissions, but I still suspect it will fail |
Looks like the same.
Yes, it works. |
Automatic merge from submit-queue (batch tested with PRs 17744, 17840, 17874). add swagger permissions Fixes permission problem from #17872 /assign php-coder /assign simo5 @openshift/sig-security @php-coder see if this gets you to the next failure.
…t-gvk-parsing Automatic merge from submit-queue (batch tested with PRs 53895, 58013, 58466, 58531, 58535). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. tolerate more than one gvklist item Some third-party resources could be part of more than one api group. Allow this to be the case when adding openapi models to openapi data, and default to the first item as the gvk key for that model. Related downstream issue: openshift/origin#17872 **Release note**: ```release-note NONE ``` cc @deads2k @soltysh
…t-gvk-parsing Automatic merge from submit-queue. UPSTREAM: 58466: tolerate more than one gvklist item Fixes #17872 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1536845 Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1529447 Origin resources, like deployment configs, are part of two api groups - the legacy "empty" group, and, in cases like deploymentconfigs, the "apps.openshift.io" group. **Before** ``` $ oc explain dc error: Couldn't find resource for "/v1, Kind=DeploymentConfig" ``` **After** ``` $ oc explain dc DESCRIPTION: 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, ... ``` cc @deads2k @soltysh
oc explain
doesn't work anymore on the latest version:Version
oc v3.9.0-alpha.0+1c24d18-233-dirty
kubernetes v1.8.1+0d5291c
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://10.34.129.148:8443
openshift v3.9.0-alpha.0+1c24d18-233-dirty
kubernetes v1.8.1+0d5291c
Steps To Reproduce
oc cluster up --version=latest
oc explain Pod
Current Result
Expected Result
Pod schema should be displayed.
The text was updated successfully, but these errors were encountered: