From c4a51a2ecca4ae151c5c16a0dc817b6704094b0d Mon Sep 17 00:00:00 2001 From: Sascha Grunert Date: Thu, 16 Jan 2020 15:48:25 +0100 Subject: [PATCH] Add note about service CIDR bug to changes (#18489) Signed-off-by: Sascha Grunert --- content/en/docs/setup/release/notes.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/en/docs/setup/release/notes.md b/content/en/docs/setup/release/notes.md index d96a1dbc01..60d49c0f3a 100644 --- a/content/en/docs/setup/release/notes.md +++ b/content/en/docs/setup/release/notes.md @@ -83,6 +83,7 @@ The Kubernetes in-tree storage plugin to Container Storage Interface (CSI) migra - volumeDevices mapping ignored when container is privileged - The `Should recreate evicted statefulset` conformance [test](https://github.com/kubernetes/kubernetes/blob/master/test/e2e/apps/statefulset.go) fails because `Pod ss-0 expected to be re-created at least once`. This was caused by the `Predicate PodFitsHostPorts failed` scheduling error. The root cause was a host port conflict for port `21017`. This port was in-use as an ephemeral port by another application running on the node. This will be looked at for the 1.18 release. - client-go discovery clients constructed using `NewDiscoveryClientForConfig` or `NewDiscoveryClientForConfigOrDie` default to rate limits that cause normal discovery request patterns to take several seconds. This is fixed in https://issue.k8s.io/86168 and will be resolved in v1.17.1. As a workaround, the `Burst` value can be adjusted higher in the rest.Config passed into `NewDiscoveryClientForConfig` or `NewDiscoveryClientForConfigOrDie`. +- The IP allocator in v1.17.0 can return errors such as `the cluster IP for service is not within the service CIDR ; please recreate` in the logs of the kube-apiserver. The cause is incorrect CIDR calculations if the service CIDR (`--service-cluster-ip-range`) is set to bits lower than `/16`. This is fixed in http://issue.k8s.io/86534 and will be resolved in v1.17.1. ## Urgent Upgrade Notes