-
Notifications
You must be signed in to change notification settings - Fork 405
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
[BUG] You must be logged in to the server (the server has asked for the client to provide credentials #508
Comments
@SataQiu Thank you for raising issue. |
tunnel-agent logs:
|
Same issue when I try to convert cluster with the
tunnel-agent logs:
|
After some digging, I found this bug is caused by "key usage" missing of the
If I am not wrong, the certificate of openyurt/pkg/yurttunnel/pki/certmanager/certmanager.go Lines 84 to 97 in f434c7f
It works again after adding |
@SataQiu @DrmagicE I'd like to use commit: 6926d2ae319d2b66b906eac4cd5454a9a32015d2 to release images of OpenYurt v0.5.0 again in order to make yurt-tunnel work. |
@rambohe-ch Yes, I think we should. |
@DrmagicE @SataQiu OpenYurt v0.5.0 images have been updated based on commit: 6926d2a |
What happened:
When I upgraded OpenYurt to the latest version(v0.5.0), I found that
kubectl logs
could not work properly and the following error occurred:What you expected to happen:
kubectl logs
can work well.How to reproduce it (as minimally and precisely as possible):
Install OpenYurt v0.5.0 in kubernetes 1.20.2.
Anything else we need to know?:
Environment:
kubectl version
): v1.20.2cat /etc/os-release
):uname -a
):others
/kind bug
The text was updated successfully, but these errors were encountered: