Skip to content
This repository has been archived by the owner on Jan 3, 2023. It is now read-only.

Creating multi-cluster ingresses fail in kubernetes 1.10.0 release #175

Open
nikhiljindal opened this issue Apr 4, 2018 · 0 comments
Open

Comments

@nikhiljindal
Copy link
Contributor

Ref kubernetes/ingress-gce#182

Due to a regression in ingress-gce controller, creating multi-cluster ingresses fail with kubernetes clusters with version 1.10.0. Existing MCIs will continue to work if they are not updated. Users will however see lots of errors in their ingress-gce controller logs.
The issue will be fixed in 1.10.1 release.

Filing this for visibility in case users run into this and search about it in this repo.

cc @G-Harmon @nicksardo

k8s-github-robot pushed a commit to kubernetes/kubernetes that referenced this issue Apr 9, 2018
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 GoogleCloudPlatform/k8s-multicluster-ingress#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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant