Merge pull request #62129 from nikhiljindal/releaseNote

Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Adding a release note in 1.10.0 for kubemci failure Ref https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/issues/175 We found an issue in ingress-gce controller due to which creating multi-cluster ingresses with kubemci fails. We have now fixed the issue. Adding a release note in 1.10.0 for visibility. ```release-note NONE ``` cc @G-Harmon @nicksardo

Merge pull request #62129 from nikhiljindal/releaseNote
8eb156fe · Kubernetes Submit Queue · GitHub · 6348e0b3 · 84ec3eb5 · 8eb156fe
Unverified Commit 8eb156fe authored Apr 09, 2018 by Kubernetes Submit Queue Committed by GitHub Apr 09, 2018
Hide whitespace changes
Inline Side-by-side

Showing with 2 additions and 0 deletions

CHANGELOG-1.10.md CHANGELOG-1.10.md +2 -0

No files found.
--- a/CHANGELOG-1.10.md
+++ b/CHANGELOG-1.10.md
@@ -300,6 +300,8 @@ kind: KubeProxyConfiguration
 * Some users, especially those with very large clusters, may see higher memory usage by the kube-controller-manager in 1.10. ([#61041](https://github.com/kubernetes/kubernetes/issues/61041))
+* Due to an issue in ingress-gce controller in 1.10.0, creating multi-cluster ingresses with [kubemci CLI](https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress) fails. This will be fixed in 1.10.1 release. ([GoogleCloudPlatform/k8s-multicluster-ingress#175](https://github.com/GoogleCloudPlatform/k8s-multicluster-ingress/issues/175))
 ## Deprecations
 * etcd2 as a backend is deprecated and support will be removed in Kubernetes 1.13.