-
Notifications
You must be signed in to change notification settings - Fork 407
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
[yurt-tunnel]improve the usage of certificates #410
Comments
It seems that the issue is not assigned to anyone yet. I would assign it to myself now, if there is any problem, please let me know. |
/assign |
@joker-joker-joker Very appreciate you for taking over this feature. /assign @joker-joker-joker |
After I modify the code, according to the https://github.com/khalid-jobs/openyurt/blob/master/docs/tutorial/yurt-e2e-test.md, if I pass |
/assign |
It seems that the openyurt's action does not have a auto e2e(start a new cluster using the latest code) like kubeedge? https://github.com/kubeedge/kubeedge/runs/3573841016?check_suite_focus=true. I think this is very helpful for developer to test. |
@ke-jobs Now we need to prepare a openyurt cluster and check the logs of openyurt components(like yurthub or yurt-tunnel) to check that components work normally or not. now github actions for OpenYurt only check |
we need to specify the usage of certificates of yurt-tunnel components clearly. Refs #410
we need to specify the usage of certificates of yurt-tunnel components clearly. Refs openyurtio#410
What would you like to be added:
There are no restrictions on the use of yurt-tunnel certificates, the code reference is:
https://github.com/openyurtio/openyurt/blob/master/pkg/yurttunnel/pki/certmanager/certmanager.go#L147-L149
we need to specify the usage of certificates of yurt-tunnel components clearly.
Why is this needed:
In order to reduce the risk of certificate safety, It's not recommended to define
any
usage for certificates.others
/kind feature
The text was updated successfully, but these errors were encountered: