-
Notifications
You must be signed in to change notification settings - Fork 162
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
Update to Kubernetes 1.11 #1198
Conversation
- "On" | ||
- "Off" | ||
- "Auto" | ||
- "Off" |
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 file change is just for testing. Don't merge me.
@linki what is the impact of switching to ipvs? We should have a good understanding of how it works and what the benefits/drawbacks are. |
@hjacobs It claims to be more performant and seems to become the default option going forward. From the release notes: "This change delivers better network throughput, better programming latency, and higher scalability limits for the cluster-wide distributed load-balancer that comprises the Kubernetes Service model" However, there's a known-issue in Kubernetes 1.11 so I think we should wait for the next release. I was just curious if e2e would pass: it does. |
@linki maybe we want not to switch to ipvs kubernetes/kubernetes#57841. |
@szuecs yes, it's mentioned as a known issue in the release notes as well. We should wait. |
Yes, this sounds like quite a serious problem :) |
Signed-off-by: Mikkel Oscar Lyderik Larsen <m@moscar.net> # Conflicts: # cluster/manifests/kube-proxy/daemonset.yaml # cluster/node-pools/master-default/userdata.clc.yaml # cluster/node-pools/worker-default/userdata.clc.yaml
* `ExpandPersistentVolumes` https://kubernetes.io/blog/2018/07/12/resizing-persistent-volumes-using-kubernetes/?utm_source=cncf&utm_medium=email&utm_campaign=cloudnativemonthly&utm_content=july18 * `CustomResourceSubresources` https://kubernetes.io/docs/tasks/access-kubernetes-api/custom-resources/custom-resource-definitions/#subresources Signed-off-by: Mikkel Oscar Lyderik Larsen <m@moscar.net>
Signed-off-by: Mikkel Oscar Lyderik Larsen <m@moscar.net>
Kube 1.11 patch
mode: 0644 | ||
contents: | ||
inline: yes | ||
{{end}} |
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.
We should fix the docker version again. I would like to try out docker 17 as 18 isn't officially supported.
Furthermore the new (better) way of defining versions for those bundled binaries is using torcx
: https://coreos.com/blog/toward-docker-17-in-container-linux
Dev to kube 1.11
Remove the `--allow-privileged` flag from the kubelet since it now defaults to `true` and has been marked deprecated and will be removed in v1.13. kubernetes/kubernetes#63442 Signed-off-by: Mikkel Oscar Lyderik Larsen <mikkel.larsen@zalando.de>
Remove deprecated --allow-privileged kubelet flag
Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
Dev to kube 1.11
Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
Dev to kube 1.11
Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
Dev to kube 1.11
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
dev-to-kube-1.11
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
dev-to-kube-1.11
Signed-off-by: Sandor Szücs <sandor.szuecs@zalando.de>
dev-to-kube-1.11
Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
Signed-off-by: Alexey Ermakov <alexey.ermakov@zalando.de>
Use the latest Docker version by default
Update to v1.11.3
Signed-off-by: Mikkel Oscar Lyderik Larsen <mikkel.larsen@zalando.de>
dev-to-kube-1.11
👍 |
👍 |
Let's see what the e2es have to say about this.
Changes:
Switch from KubeProxy'siptables
mode toipvs
modeDisable docker version change, therefore it uses 18.03.x with the AMI above which is not officially supported by Kubernetes 1.11 (let's see where we end up; 1.12 and 17.03.x work fine and are supported)PersistentVolumeClaimResize
feature flag (enabled by default)CustomResourceSubresources
feature gate (enabled by default).