-
Notifications
You must be signed in to change notification settings - Fork 893
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
docs: add proposal of karmadactl init support config file #5277
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5277 +/- ##
==========================================
+ Coverage 28.38% 35.19% +6.81%
==========================================
Files 632 645 +13
Lines 43801 44869 +1068
==========================================
+ Hits 12432 15791 +3359
+ Misses 30464 27847 -2617
- Partials 905 1231 +326
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
/assign @liangyuanpeng @zhzhuang-zju |
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks you for opening it! I will check it later!
I have completed the implementation code section and updated the reviewer section at the beginning of the document. Professor, could you please check it when you have time? |
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
/retest |
@tiansuo114: Cannot trigger testing until a trusted user reviews the PR and leaves an 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. |
/ok-to-test |
/retest |
f7cb586
to
2ee63b6
Compare
May need help😭😭, in my own project's github action, these tests passed correctly, but when I commit, these tests become failed, what should I do to fix these problems |
This is not releated with this PR, have some pull rate limit from dockerhub (: , just run command /ok-to-test |
BTW, this is a proposal PR, have not change code, so you don’t need to worry about CI because there is no document-related CI |
/lgtm |
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No doubt that this is a high-quality proposal, thanks for your effort.
Just leave some comments and questions.
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
KubeConfigPath string yaml:"kubeConfigPath" | ||
KubeImageTag string yaml:"kubeImageTag" | ||
KubeContextName string yaml:"context" | ||
KubeStorageClassesName string yaml:"storageClassesName" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you remind me which flag the KubeStorageClassesName
applies to?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here are some of the early design error, in the back I changed, but when the synchronization in the document missing, the name should be StorageClassesName, used to fill the CommandInitOption. StorageClassesName
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. By the way, can you add some comments to the structure? If there is a corresponding flag, please also put it in comments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, so far, I have only added explanatory comments before each general structure, but I think the information in the corresponding fields of each structure should confirm their purpose. In your opinion, where should you add comments about the corresponding flag? Do you mean the corresponding flag of which configuration items?
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
...dactl Supports Configuration File Method for Production-Grade Installation and Deployment.md
Outdated
Show resolved
Hide resolved
/retest |
|
||
As Karmada is widely used in multi-cluster management, the current `karmadactl init` command has accumulated dozens of command-line parameters. This not only increases the learning curve for users but also reduces the convenience of usage. With the ongoing development of the community, the number and complexity of these parameters are likely to continue growing, further impacting the user experience. | ||
|
||
Additionally, during the deployment process of `karmadactl init`, multiple container images are needed. Users may want to download the corresponding images in advance to save deployment time, but currently, there is no easy way for users to obtain the list of required container images. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shall we move this part out of this proposal?
|
||
Therefore, I think the configuration file can be designed to focus on these parts, structuring the YAML accordingly, and incorporating the existing configuration items into them. Additionally, similar to the commonly used `Extra Arg` field in Kubernetes structures, an extra field can be added to store other general fields. When designing the fields, it is advisable to refer to the field names in the kubeadm configuration file as much as possible, to facilitate user familiarity and quick adoption. | ||
|
||
After completing the design for reading config files in `karmada init`, we can extend the functionality of the `karmadactl config image list` command to read the required image configuration from the config file by reusing the config file reading method. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ditto.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, these parts need to be deleted. Maybe I lost the commit of the deleted part when I was rebase. I will modify this part as soon as possible
Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> add Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> add file change Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix doc Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix comment Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com> fix Signed-off-by: tiansuo114 <1729765480@qq.com>
I have already modified this document according to the discussion requirements from the meeting. When you have time, please kindly review it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What type of PR is this?
/kind feature
What this PR does / why we need it:
karmadactl supports configuration file installation and deployment
Which issue(s) this PR fixes:
Parts of #3464
Special notes for your reviewer:
Does this PR introduce a user-facing change?: