-
Notifications
You must be signed in to change notification settings - Fork 885
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
[Summer OSPP 2024] karmadactl init supports configuration file #5387
Comments
/assign |
Here is the documentation for karmadactl changes Supplement pr |
@tiansuo114 Congrats! All tasks have been done. Thank you for your hard work! /close |
@RainbowMango: Closing this issue. In response to this:
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-sigs/prow repository. |
The PR related to tests has been changed to the PR at #5306. Should we update the documentation to reflect this? |
sure, i updated it, thank you! |
Thank you very much, Mentor, for your guidance over the past few months in completing the OSPP tasks. I am truly grateful for all the help you've provided, and I hope to receive even more guidance from you in future PRs |
What would you like to be added
As the community grows, karmada has more and more components and the configuration required is becoming more and more complex. Karmada hopes to transfer configuration items to the configuration file instead of more and more flags.
At the same time, it is hoped that a function that can list all container images used in the karmadactl init process can be implemented.
Releated:
This is part of #4879
Changed
we decide pause to work for feature of
karmadactl image list
based on the content of the meetingProject link
https://summer-ospp.ac.cn/org/prodetail/245c40186?lang=zh&list=pro
Desired outcomes
karmadactl config images list
Add GitHub tests for karmadactl init --config command #5306metadata
(included in Add GitHub tests for karmadactl init --config command #5306)The text was updated successfully, but these errors were encountered: