-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
istio ingress gw doesn't reach running on remote cluster #23859
Comments
|
what exactly is our status port, the log has
|
I think you have the wrong version running |
That was it, sorry forgot to remove hub and tag from my io. Thank you @howardjohn !! |
I am still seeing issues with my ingress gw on remote cluster:
|
Not sure if anyone else hit it... I think the ingress gw did come up it just take slightly longer (60+s) thus it was not marked as ready. |
may need to tweak this slightly longer for ingress gw as it does take a while to come up - https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-startup-probes |
Lin the time it takes does not matter, it could take 1 hr and once it becomes ready it will be marked ready. Can you post the full logs when it's slow to get ready maybe? |
I need to test this without centralIstiod but I think the ingress gw doesn't reach running was due to citadel agent on the gw can't get the certs via CSR. @irisdingbj I think you forgot to cherry pick https://github.com/istio/istio/pull/22989/files to release-1.6.
|
@linsun 22989 is in 1.6 . It is checked in before we cut 1.6 branch . So it does not need a cherry-pick PR |
Found out this is caused by port 15012 is not opened up by default. By having the following in the yaml will solve it.
can update doc for this. |
It appears some change from #23102 broke my sleep container on remote cluster from reaching running. @irisdingbj is going to follow up with @hzxuzhonghu on this.
|
This ingress gw issue is fixed by adding caAddress in the remote yaml config (see istio/istio.io#7243). With that, ingress gw can reach running. The sidecar not reach running issue is tracked under #23879 |
Bug description
The log look fine, I think it is just an status for the port failed.
Expected behavior
ingress gw reaches running
Steps to reproduce the bug
Version (include the output of
istioctl version --remote
andkubectl version
andhelm version
if you used Helm)1.6.0 rc.0
How was Istio installed?
Followed the example here on the primary cluster: istio/istio.io#7243, step 1.
Environment where bug was observed (cloud vendor, OS, etc)
IKS 1.16
The text was updated successfully, but these errors were encountered: