-
Notifications
You must be signed in to change notification settings - Fork 39.8k
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
[Federation][Kubefed] Flag cleanup #41335
[Federation][Kubefed] Flag cleanup #41335
Conversation
|
/approve |
@spxtr Why are you trying to approve this? |
@marun I only approved changes to |
@spxtr Thank you for explaining. I hadn't fully grokked the path-based nature of the new approval mechanism. |
@irfanurrehman Since federation doesn't work, at least the service controller doesn't work, without a valid |
c08d2ee
to
ed651f8
Compare
ed651f8
to
7f5b7de
Compare
@madhusudancs updated PTAL! |
@k8s-bot kops aws e2e test this |
@k8s-bot cvm gce e2e test this |
federation/cluster/federation-up.sh
Outdated
@@ -82,7 +82,8 @@ function init() { | |||
"${FEDERATION_NAME}" \ | |||
--host-cluster-context="${HOST_CLUSTER_CONTEXT}" \ | |||
--dns-zone-name="${DNS_ZONE_NAME}" \ | |||
--image="${kube_registry}/hyperkube-amd64:${kube_version}" | |||
--image="${kube_registry}/hyperkube-amd64:${kube_version}" \ | |||
--apiserver-arg-overrides="--storage-backend=etcd2" |
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.
Now that kubefed init
is no longer specifying etcd2
as the default, a user will get the underlying default of etcd3
unless they specify the same override as appears here. Why is it desirable that federation-up.sh
not use etcd3
as well?
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 am not sure, if enough analysis or update (if there is any that is needed) is done in the federation API server code to move to etcd3.
Given the previous, trying to be cautious not to break something.
as far as I know @madhusudancs and @shashidharatd found some issues with using etcd3 backend; probably they can comment better.
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.
Then why is this PR proposing to default kubefed
to etcd3? That would seem to risk breaking users.
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.
Why would it break a user who is running kubefed init
? kubefed init
brings up a new control plane and people who bring up new control planes can choose etcd3
. We don't have upgrade support yet.
Should we also test with etcd3
? Yes. And that's coming. I am asking people to not make too many disruptive changes at this point. We are trying really hard to get the CI tests to a green state.
/lgtm Reviewed 1 of 7 files at r1, 1 of 4 files at r2, 3 of 7 files at r3, 1 of 1 files at r4. Comments from Reviewable |
7f5b7de
to
93a73c3
Compare
@madhusudancs has to rebase to remove conflicts, need the lgtm again. thanks! |
@irfanurrehman unfortunately, it needs a rebase again. Please ping me on IM as soon as you rebase this. |
93a73c3
to
93a1980
Compare
@madhusudancs rebased, PTAL! |
/lgtm Review status: 0 of 4 files reviewed at latest revision, 1 unresolved discussion. Comments from Reviewable |
…bring up federation
93a1980
to
f183283
Compare
@madhusudancs had to rebase once more.. :(, PTAL! |
@k8s-bot kops aws e2e test this |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED The following people have approved this PR: irfanurrehman, k8s-merge-robot, madhusudancs, spxtr Needs approval from an approver in each of these OWNERS Files:
You can indicate your approval by writing |
@kubernetes/release-admins @idvoretskyi @calebamiles We added a new flag in 1.6 cycle that we want to remove before the release goes out. This PR removes the flag. The PR was reviewed and ready before code freeze but was struck in the rebase hell. I also forgot to add the label before. Could we get an exception for this one? |
Automatic merge from submit-queue (batch tested with PRs 42200, 39535, 41708, 41487, 41335) |
This PR is for the issue #41333
Special notes for your reviewer:
@marun @madhusudancs
Release note: