kubevirt: `virtctl vnc vm` fails with 401 permission denied
Hello,
Trying out the demo, virtctl vnc vmname fails with a Error encountered: Can't connect to websocket (401): request is not authenticated.
This error ultimatively comes from the extensions apiserver and is logged as level=info timestamp=2018-06-09T11:47:20.345809Z pos=filter.go:46 component=virt-api remoteAddress=172.25.0.6 username=- method=GET url=/apis/subresources.kubevirt.io/v1alpha1/namespaces/default/virtualmachines/test-ubuntu-vm/vnc proto=HTTP/1.1 statusCode=401
I am not entirely sure how to proceed debugging from there, any hints?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Comments: 15 (13 by maintainers)
Commits related to this issue
- Authenticate apiserver when proxying This fixes https://github.com/kubevirt/kubevirt/issues/1126 by adding the --proxy-client-cert-file and --proxy-client-key-file flags — committed to kubermatic/kubermatic by alvaroaleman 6 years ago
- Authenticate apiserver when proxying (#1232) This fixes https://github.com/kubevirt/kubevirt/issues/1126 by adding the --proxy-client-cert-file and --proxy-client-key-file flags — committed to kubermatic/kubermatic by alvaroaleman 6 years ago
Ah, thanks a lot! So for the record, the required flags on the kube-apiserver are:
Where
<path to aggregator proxy cert>can be just the tls serving cert