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

Sub validator controller connectivity instability #1687

Open
Abd4llA opened this Issue Nov 16, 2018 · 2 comments

Comments

4 participants
@Abd4llA
Contributor

Abd4llA commented Nov 16, 2018

It was found on some cluster that the sub-validator stopped reacting to new EventActivations creations. The cluster was initially working fine, that symptom showed up after about 4 days.

After deeper investigation, other controllers in Kyma were working fine, restarting istio pilot didn't help, however kubelet logs were not available on that cluster.

When sub-validator pod was deleted, the new one worked fine.

Cluster: a faros provisioned 0.5rc2 cluster.

@radufa

This comment has been minimized.

Contributor

radufa commented Nov 19, 2018

An interesting aspect on that cluster was that Jaeger UI was not exported outside of cluster (error 404) which could be related to the old instability issue of Istio gateway (the Jaeger virtual service) was not reachable.

@Abd4llA

This comment has been minimized.

Contributor

Abd4llA commented Nov 19, 2018

@radufa actually it was working, Sayan was just not using the correct link from Kyma console which goes to the authentication proxy but was accessing the UI directly. We validated that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment