--insecure-skip-tls-verify do not workaround TLS issues.

[kaovilai]

Any help?

❯ oc login --server=https://api.tkaovila-gcpdev....:6443 -u kk -p pp
error: x509: “kube-apiserver-lb-signer” certificate is not trusted

~ master*
❯ oc login --server=https://api.tkaovila-gcpdev....:6443 -u kk -p pp --insecure-skip-tls-verify=true
WARNING: Using insecure TLS client config. Setting this option is not supported!

error: x509: “ingress-operator@1678304794” certificate is not trusted

❯ oc version
Client Version: 4.12.0-202208031327
Kustomize Version: v4.5.4
Unable to connect to the server: dial tcp: lookup api.tkaovila-gcpdev....: no such host

[ibihim]

I ran into a similar issue:

> oc login -u john -p doe
error: x509: “ingress-operator@1678900450” certificate is not trusted

And adding skip-verify didn't help:

> oc login -u john -p doe --insecure-skip-tls-verify=true
WARNING: Using insecure TLS client config. Setting this option is not supported!

error: x509: “ingress-operator@1678900450” certificate is not trusted

But updating my oc client helped (Client Version: v4.12.0), but running oc version always returned a host for me.

Pre-update:

> oc version
Client Version: 4.12.0-ec.5
Kustomize Version: v4.5.7
Server Version: 4.12.4
Kubernetes Version: v1.25.4+a34b9e9

Post-update:

> oc version
Client Version: v4.12.0
...

[ardaguclu]

This was an known issue which happens due to a bug in Go and it was fixed in newer releases. More info: #1207

/close

[openshift-ci]

@ardaguclu: Closing this issue.

In response to this:

This was an known issue which happens due to a bug in Go and it was fixed in newer releases. More info: #1207

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.