-
Notifications
You must be signed in to change notification settings - Fork 890
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
introduce kube-image-tag flag to karmadactl init #2840
introduce kube-image-tag flag to karmadactl init #2840
Conversation
c103729
to
91ced92
Compare
According to our current application scenario, we are more concerned about the version of kube (some problems of interface compatibility), so I limited the scope of tag parameters discussed earlier to kube. |
Codecov Report
@@ Coverage Diff @@
## master #2840 +/- ##
==========================================
+ Coverage 37.89% 38.60% +0.71%
==========================================
Files 190 206 +16
Lines 17681 18846 +1165
==========================================
+ Hits 6700 7276 +576
- Misses 10574 11140 +566
- Partials 407 430 +23
Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
/lgtm |
LGTM |
pkg/karmadactl/cmdinit/cmdinit.go
Outdated
@@ -97,6 +97,7 @@ func NewCmdInit(parentCommand string) *cobra.Command { | |||
// kube image registry | |||
flags.StringVarP(&opts.KubeImageMirrorCountry, "kube-image-mirror-country", "", "", "Country code of the kube image registry to be used. For Chinese mainland users, set it to cn") | |||
flags.StringVarP(&opts.KubeImageRegistry, "kube-image-registry", "", "", "Kube image registry. For Chinese mainland users, you may use local gcr.io mirrors such as registry.cn-hangzhou.aliyuncs.com/google_containers to override default kube image registry") | |||
flags.StringVar(&opts.KubeVersion, "kube-version", "v1.25.2", "Choose a specific Kubernetes version for the control plane.") |
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.
How about kube-image-tag
? It seems to account for the relation with kube-image-registry
.
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 these two can be a definition @lonelyCZ
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.
kubeadm
is specially to install Kubernetes that is a little different from my scenario. After all, we only two kube images, and I think kube-image-tag
, kube-image-registry
and kube-image-mirror-country
could be better togather. What do you think? @helen-frank @RainbowMango
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.
agree
What do you think? @RainbowMango
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.
kubeadm is specially to install Kubernetes that is a little different from my scenario.
Totally agree!
@helen-frank Can you help to describe why we need a new flag? I'm kind of lost from it.
We already have the following flags:
- --karmada-kube-controller-manager-image=''
- --etcd-image=''
- --etcd-init-image='docker.io/alpine:3.15.1'
- --karmada-apiserver-image=''
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.
currently, the platform cannot upgrade kube versions with karmada to adapt
What do you mean?
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.
Some of our existing business platforms have different requirements for kube versions, so there is often a requirement for setting up kube versions when using karmadactl to install karmada, while we are not particularly concerned about others. For the Karmada itself, we use the latest stable version.
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 a common situation. What do you think
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, I agree it's a reasonable case.
Do we have any other alternatives in addition to kube-image-tag and --kube-version
?
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.
At present, there is no better idea. Individuals are more inclined to kube-version
. kube-image-tag
is also acceptable.
I want to use kube-version function now. Can I continue this topic? @lonelyCZ @RainbowMango |
I think it can be move forward. Now the main question is the name of the option. Perhaps, we can vote for deciding it. I perfer |
kube-image-tag +1 |
I'm ok with it. |
In terms of contextual consistency, it seems that |
OK, everyone seems to approve |
91ced92
to
b5af5da
Compare
/cc @lonelyCZ |
@@ -92,6 +90,7 @@ type CommandInitOption struct { | |||
ImageRegistry string | |||
KubeImageRegistry string | |||
KubeImageMirrorCountry string | |||
KubeVersion string |
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.
KubeVersion string | |
KubeImageTag string |
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.
fixed
Signed-off-by: helen <haitao.zhang@daocloud.io>
b5af5da
to
5eaf574
Compare
/lgtm Thanks @helen-frank , and please update the PR description. |
/cc @RainbowMango |
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.
/approve
I updated the release notes, by the way.
[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 |
Thank you😂 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
Choose a specific Kubernetes version for the control plane.
Which issue(s) this PR fixes:
Fixes #
see #2541 #2655
Special notes for your reviewer:
TEST
Does this PR introduce a user-facing change?: