-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
WIP: kindnet + ipalias #17206
base: master
Are you sure you want to change the base?
WIP: kindnet + ipalias #17206
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
6f42dc0
to
41997ba
Compare
/test pull-kops-e2e-k8s-gce-ipalias |
if c.Spec.Networking.GCP != nil { | ||
return true | ||
} | ||
|
||
if c.Spec.Networking.Kindnet != nil { | ||
// TODO: Are we _always_ using ipalias - should we at least check the cloud is GCP? |
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.
yeah, I don't want kindnet to use overlays, there are already plenty of options ... besides, we'll focus on IPv6 for development that will not require overlays as there is plenty of space
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.
Great - I think for (pure) IPv6 we probably don't want to trigger the configuration of alias IP ranges on the instances here, but ... let's see how it goes.
kindnet is installed but the nodes are not ready https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kops/17206/pull-kops-e2e-gce-cni-kindnet/1878892464866070528/artifacts/control-plane-us-west4-c-bwxs/kube-scheduler.log
The kube-controller-manager is also running an ipam controller
and the cloud-controller-manager is also running
what version of the cloud controller manager are we running, that seems buggy, since is trying to allocate two cirds of the same family, or maybe is trying to append ... independently, there can be only one ipam controller running at a time and it should be type CloudAllocator |
e7ed9b1
to
670c065
Compare
Tweaked the logic in /kubecontrollermanager.go to turn off some controllers when using kindnet, similar to what we do with "GCE" network (which is really ip alias networking) |
/test pull-kops-e2e-gce-cni-kindnet |
/retest Looks like a MIG naming collision:
|
/test pull-kops-e2e-gce-cni-kindnet Same weird flake |
|
||
// If the cloud is allocating the node CIDRs, that should be done by CCM | ||
if o.GetCloudProvider() == kops.CloudProviderGCE && gce.UsesIPAliases(o) { | ||
kcm.AllocateNodeCIDRs = fi.PtrTo(false) |
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 is not working, is sitll allocating ips https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kops/17206/pull-kops-e2e-gce-cni-kindnet/1878987987832803328/artifacts/control-plane-us-west3-c-qr8f/kube-controller-manager.log
I0114 02:32:44.480427 11 flags.go:64] FLAG: --allocate-node-cidrs="true"
I0114 02:32:44.480848 11 flags.go:64] FLAG: --allow-metric-labels="[]"
I0114 02:32:44.480874 11 flags.go:64] FLAG: --allow-metric-labels-manifest=""
I0114 02:32:44.480882 11 flags.go:64] FLAG: --allow-untagged-cloud="false"
I0114 02:32:44.480888 11 flags.go:64] FLAG: --attach-detach-reconcile-sync-period="1m0s"
I0114 02:32:44.480896 11 flags.go:64] FLAG: --authentication-kubeconfig="/var/lib/kube-controller-manager/kubeconfig"
I0114 02:32:44.481142 11 flags.go:64] FLAG: --authentication-skip-lookup="false"
I0114 02:32:44.481322 11 flags.go:64] FLAG: --authentication-token-webhook-cache-ttl="10s"
I0114 02:32:44.481332 11 flags.go:64] FLAG: --authentication-tolerate-lookup-failure="false"
I0114 02:32:44.481338 11 flags.go:64] FLAG: --authorization-always-allow-paths="[/healthz,/readyz,/livez]"
I0114 02:32:44.481683 11 flags.go:64] FLAG: --authorization-kubeconfig="/var/lib/kube-controller-manager/kubeconfig"
I0114 02:32:44.481694 11 flags.go:64] FLAG: --authorization-webhook-cache-authorized-ttl="10s"
I0114 02:32:44.481702 11 flags.go:64] FLAG: --authorization-webhook-cache-unauthorized-ttl="10s"
I0114 02:32:44.481707 11 flags.go:64] FLAG: --bind-address="0.0.0.0"
I0114 02:32:44.481716 11 flags.go:64] FLAG: --cert-dir=""
I0114 02:32:44.481721 11 flags.go:64] FLAG: --cidr-allocator-type="RangeAllocator"
670c065
to
a663d8b
Compare
/test pull-kops-e2e-gce-cni-kindnet |
1 similar comment
/test pull-kops-e2e-gce-cni-kindnet |
@justinsb: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. I understand the commands that are listed here. |
it failed twice the same test, I need to debug this |
trying to repro so we avoid the roundtrip, we'll keep you posted |
/test pull-kops-e2e-gce-cni-kindnet |
@justinsb it is green now |
Well that's good, I guess! Do we think that's because of the MTU change, something you fixed, or maybe just a flake? If MTU, I think the default is 1460 - should we use a different value (e.g. the more standard 1500?). Or should kindnet (and all CNIs) pick up the current MTU? Or both? :-) |
dccad14
to
c9d4e28
Compare
No description provided.