InsecureSkipTLSVerifyBackend was backported to origin to be able to read the logs even when certificate is broken. This ensure that we can almost always read the logs.
Fixed in https://github.com/openshift/oc/pull/207
Confirmed with latest oc client, the issue has fixed: [root@dhcp-140-138 logs]# oc version -o yaml clientVersion: buildDate: "2019-12-16T10:31:48Z" compiler: gc gitCommit: ff590d4496deedc069232984c20b4e5159c43b28 gitTreeState: clean gitVersion: v4.4.0 goVersion: go1.12.12 major: "" minor: "" platform: linux/amd64 oc adm inspect co network --loglevel=9 |& tee /tmp/ins Check the logs, could see: I1218 14:16:29.653401 23210 request.go:538] Throttling request took 1.100721319s, request: GET:https://api.xiyuan-12167.qe.devcluster.openshift.com:6443/api/v1/namespaces/openshift-sdn/pods/ovs-8hhmr/log?container=openvswitch&insecureSkipTLSVerifyBackend=true&previous=true×tamps=true I1218 14:16:29.653482 23210 round_trippers.go:423] curl -k -v -XGET -H "Accept: application/json, */*" -H "User-Agent: oc/v0.0.0 (linux/amd64) kubernetes/$Format" 'https://api.xiyuan-12167.qe.devcluster.openshift.com:6443/api/v1/namespaces/openshift-sdn/pods/ovs-8hhmr/log?container=openvswitch&insecureSkipTLSVerifyBackend=true&previous=true×tamps=true'
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