Skip to content
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

K8S Dashboard loads slowly, tiller unresponsive once istio 1.0.0 installed #605

Closed
BernhardRode opened this issue Aug 15, 2018 · 11 comments
Closed

Comments

@BernhardRode
Copy link

What happened:
K8S Dashboard loads slowly, tiller unresponsive once istio 1.0.0 installed.
What you expected to happen:
K8S Dashboard and helm should still be usable after Istio installation.
How to reproduce it (as minimally and precisely as possible):

  • Kubernetes version (use kubectl version):
    v1.11.1
  • Size of cluster (how many worker nodes are in the cluster?)
    6 x Standard Standard_D2_v2
  • General description of workloads in the cluster
    HTTP microservices
@mboersma
Copy link
Member

We identified a problem with a read timeout value that is fixed now in AKS. New clusters should not see this problem when installing Istio. For any existing clusters that see this problem, please open a support ticket directly with Azure support, or email [email protected] with details so we can patch up your cluster.

@ChrisPei
Copy link

same issues

@ChrisPei
Copy link

I found that kube-dashboard can't start kubernetes-dashboard-key-holder-kube-system when istio has been installed.

kube-dashbaord always stuck here:

2018/08/16 03:38:58 Using in-cluster config to connect to apiserver
2018/08/16 03:38:58 Starting overwatch
2018/08/16 03:38:58 Using service account token for csrf signing
2018/08/16 03:38:58 No request provided. Skipping authorization

But when I delete istio, kube-dashboard pod will continue immediately:

2018/08/16 04:00:08 Starting overwatch
2018/08/16 04:00:08 Using in-cluster config to connect to apiserver
2018/08/16 04:00:08 Using service account token for csrf signing
2018/08/16 04:00:08 No request provided. Skipping authorization
2018/08/16 04:00:40 Successful initial request to the apiserver, version: v1.11.1
2018/08/16 04:00:40 Generating JWE encryption key
2018/08/16 04:00:40 New synchronizer has been registered: kubernetes-dashboard-key-holder-kube-system. Starting
2018/08/16 04:00:40 Starting secret synchronizer for kubernetes-dashboard-key-holder in namespace kube-system
2018/08/16 04:00:45 Initializing JWE encryption key from synchronized object

@BernhardRode
Copy link
Author

I've received a mail from microsoft tonight.

Please have a look at this:
istio/istio#7675 (comment)

If my tests pass, this ticket may be closed from my side.

@ChrisPei
Copy link

@BernhardRode I'm still waiting the reply from microsoft. Hope that is the right way to resolve this issues.

@BernhardRode
Copy link
Author

BernhardRode commented Aug 17, 2018

So after some hours the issue is back ... dashboard and helm are not usable anymore.

See the details: istio/istio#7675 (comment)

@BernhardRode
Copy link
Author

The issue seems to be fixed in istio 1.0-release branch. So with the next upcoming release, we should be fine.

istio/istio#7675

@rsnj
Copy link

rsnj commented Aug 23, 2018

I am still experiencing this issue with the nightly Istio release. Looks like it may be an issue with the AKS Api Server.
istio/istio#7675 (comment)

@BernhardRode
Copy link
Author

I'm sorry ... @rsnj is right. After leaving the cluster alone for some hours the problem is back.

@BernhardRode BernhardRode reopened this Aug 24, 2018
@subesokun subesokun mentioned this issue Aug 27, 2018
@lachie83
Copy link
Member

Related to - #620

@BernhardRode
Copy link
Author

I think we can close the issue and watch the changes in #620.

@ghost ghost locked as resolved and limited conversation to collaborators Aug 1, 2020
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

5 participants