+++ This bug was initially created as a clone of Bug #1477957 +++ Description of problem: all links got 404 in "oc explain pods" Version-Release number of selected component (if applicable): openshift v4.1.4 How reproducible: Always Steps to Reproduce: 1. oc explain pods 2. open any link Actual results: 404 page not found Expected results: right web page displayed Additional info:
Mike, since you're the expert, it looks like api-convetions moved to https://git.k8s.io/community/contributors/devel/api-conventions.md not sure what else moved along with it.
Oh man these links look broken everywhere in the upstream API, seems they moved to https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md https://github.com/kubernetes/api/search?q=https%3A%2F%2Fgit.k8s.io%2Fcommunity%2Fcontributors%2Fdevel%2Fapi-conventions.md&unscoped_q=https%3A%2F%2Fgit.k8s.io%2Fcommunity%2Fcontributors%2Fdevel%2Fapi-conventions.md 84 results using the wrong link
I haven't been able to fetch or push to k8s repos all day, don't know why (it's only k8s). I opened an upstream issue to track this and hopefully will be able to actually make the change https://github.com/kubernetes/kubernetes/issues/81526
This is apparently being worked on in this PR: https://github.com/kubernetes/kubernetes/pull/74245 however that was opened in February and it's been pretty quiet from the author since... hopefully it gets an update soon
This requires a bigger change, we'll have to live with the current not working links, moving this to 4.3
This should be fixed now
Confirmed with latest oc client, the issue has fixed: [root@dhcp-140-138 ~]# oc version Client Version: v4.3.0 Server Version: 4.3.0-0.nightly-2019-10-29-140935 Kubernetes Version: v1.16.2 [root@dhcp-140-138 ~]# oc explain services KIND: Service VERSION: v1 DESCRIPTION: Service is a named abstraction of software service (for example, mysql) consisting of local port (for example 3306) that the proxy listens on, and the selector that determines which pods will answer requests sent through the proxy. 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 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 spec <Object> Spec defines the behavior of a service. https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status status <Object> Most recently observed status of the service. Populated by the system. Read-only. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status All the links can be opened.
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:0062