-
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
Feature: karmadactl init supports deployment through configuration files #5357
Conversation
Hi, this is a bot comment, just put the label of /ok-to-test |
please link to the proposal at PR describe.
|
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5357 +/- ##
==========================================
+ Coverage 41.37% 41.53% +0.16%
==========================================
Files 651 653 +2
Lines 55265 55484 +219
==========================================
+ Hits 22868 23048 +180
- Misses 30917 30949 +32
- Partials 1480 1487 +7
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This PR is related to the documentation PR: #5277 |
Ok, I've now connected all three related PRS to document pr |
Can we start the review of this pr first, or do we still need to wait for the merge of #5277 before we can conduct the review of this pr |
I think we need to merge proposal first |
The code in this branch has been modified to use the configuration file format from the existing proposal for deployment, and it has been verified that the deployment works correctly. Additionally, the proposal has already been merged into the master branch. Can we start the review now? Furthermore, I have some questions in another PR, and we might need to discuss them further. |
0e29649
to
44a25dc
Compare
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.
sorry for my later and add some comment
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.
This PR first reads the configuration file and then convert to CommandInitOption
, which is compatible with the legacy code unless you refactor the legacy code logic. Do you agree?
Yeah, I agree. |
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.
Generally looks good to me after a quick go-through. Just some nits about naming convention.
@liangyuanpeng do you have any further comments?
@tiansuo114 Have you tested it? Can you share the test report here?
3ce103c
to
1e85a8a
Compare
I conducted some tests using kind cluster in a virtual machine on my local machine. I also attempted to add a test task in the CLI section of Karmada's GitHub CI workflow to verify whether the karmadactl init --init-config command runs correctly. (The detailed testing process can first be observed in this link)Following the guidance of my mentor, I plan to submit a separate PR to merge the test process into the main branch after the current PR is merged. |
OK. |
e18005e
to
0e0115b
Compare
16717ca
to
bdde118
Compare
/retest |
Signed-off-by: tiansuo114 <1729765480@qq.com> fix lint Signed-off-by: tiansuo114 <1729765480@qq.com>
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
Hi @liangyuanpeng Let's move this forward and handle further comments by separated PRs.
[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 |
Hi, this is a bot comment, just put the label of /ok-to-test |
// KarmadaInitConfig defines the configuration for initializing Karmada | ||
type KarmadaInitConfig struct { | ||
metav1.TypeMeta `json:",inline" yaml:",inline"` | ||
metav1.ObjectMeta `json:"metadata,omitempty" yaml:"metadata,omitempty"` |
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.
I think this is not need, let's delete 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.
Do you mean the metav1.ObjectMeta
? It makes sense to me.
Please add a task to the tracking issue.
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.
Updated, How about including it in #5306 (comment) (for Summer OSPP 2024)?, or alone PR for 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.
Both are OK to me. I just want somewhere track this.
What type of PR is this?
/kind feature
What this PR does / why we need it:
Increased karmadactl's ability to init by reading configuration files
From
Turn into
Example of config.yaml
Which issue(s) this PR fixes:
Fixes #3464
This PR is related to the documentation PR: #5277
Special notes for your reviewer:
@liangyuanpeng
Does this PR introduce a user-facing change?: