Skip to content

Heapster Addon #873

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.

Sign up for GitHub

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

Jump to bottom
Closed
arun-gupta opened this issue Dec 1, 2016 · 8 comments
Closed

Heapster Addon #873

arun-gupta opened this issue Dec 1, 2016 · 8 comments
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@arun-gupta
Copy link

arun-gupta commented Dec 1, 2016 •
edited
Loading

Following up from #743

Installing Heapster add as:

865 > minikube addons enable heapster
heapster was successfully enabled
865 > minikube addons open heapster
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Waiting, endpoint for service is not ready yet...
Could not find finalized endpoint being pointed to by monitoring-grafana: Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet
Temporary Error: Endpoint for service is not ready yet

The command exits without showing any success/pass message. This is confusing and makes me wonder that command didn't succeed.

In addition, the pods never start successfully:

kubectl get pods -w --all-namespaces
NAMESPACE     NAME                          READY     STATUS              RESTARTS   AGE
kube-system   heapster-ldpza                0/1       ContainerCreating   0          3m
kube-system   influxdb-grafana-yzzbw        0/2       ContainerCreating   0          3m
kube-system   kube-addon-manager-minikube   1/1       Running             0          6m
kube-system   kube-dns-v20-c9fog            0/3       ContainerCreating   0          3m
kube-system   kubernetes-dashboard-g7r4q    1/1       Running             0          3m
@r2d4 r2d4 added the kind/bug Categorizes issue or PR as related to a bug. label Dec 1, 2016
@arun-gupta
Copy link
Author

The pod starts successfully after quite a long wait:

kubectl get pods -w --all-namespaces
NAMESPACE     NAME                          READY     STATUS    RESTARTS   AGE
kube-system   heapster-ldpza                1/1       Running   0          29m
kube-system   influxdb-grafana-yzzbw        2/2       Running   0          29m
kube-system   kube-addon-manager-minikube   1/1       Running   0          32m
kube-system   kube-dns-v20-c9fog            3/3       Running   0          29m
kube-system   kubernetes-dashboard-g7r4q    1/1       Running   0          29m

@r2d4
Copy link
Contributor

r2d4 commented Dec 1, 2016

Thats a pretty bad user experience. Maybe we can add some benchmark tests to make sure we can startup multiple addons in a reasonable time?

@aaron-prindle
Copy link
Contributor

aaron-prindle commented Dec 15, 2016 •
edited
Loading

I believe the only way to reliably speed this up would be to have a private image registry that we package hte images in and then and the pull the addons from that. I do not know if we should pursue this though as it would make the minikube binary larger.

@johnharris85
Copy link

@arun-gupta how long is a long time? I'm experiencing something similar (waiting over 30 mins so far on decent connection). The biggest problem here really is there's no way to see what's going on. Nothing in the logs, nothing in events.

In fact, I see the services, but don't see any pods at all.

$ minikube addons list
- addon-manager: enabled
- dashboard: enabled
- default-storageclass: enabled
- kube-dns: enabled
- heapster: enabled
- ingress: disabled
- registry-creds: enabled

$ kubectl get svc --all-namespaces
NAMESPACE     NAME                   CLUSTER-IP   EXTERNAL-IP   PORT(S)             AGE
default       kubernetes             10.0.0.1     <none>        443/TCP             6h
kube-system   heapster               10.0.0.134   <nodes>       80:32138/TCP        47m
kube-system   kube-dns               10.0.0.10    <none>        53/UDP,53/TCP       6h
kube-system   kubernetes-dashboard   10.0.0.165   <nodes>       80:30000/TCP        6h
kube-system   monitoring-grafana     10.0.0.53    <nodes>       80:31495/TCP        47m
kube-system   monitoring-influxdb    10.0.0.172   <none>        8083/TCP,8086/TCP   47m

$ kubectl get pods --all-namespaces
NAMESPACE     NAME                          READY     STATUS    RESTARTS   AGE
kube-system   kube-addon-manager-minikube   1/1       Running   0          6h
kube-system   kube-dns-196007617-82kgl      2/3       Error     54         6h
kube-system   kubernetes-dashboard-hqhzh    1/1       Running   0          6h
kube-system   registry-creds-4m71f          1/1       Running   0          2h

@arun-gupta
Copy link
Author

@johnharris85 This was a while back (~Dec 2016) so things may have changed. But seems like the pods came up somewhere within 29 mins.

@johnharris85
Copy link

Thanks @arun-gupta, seems like the issue I'm hitting is different, but fixed in #1513.

@vorburger
Copy link
Contributor

@r2d4 just FYI with minikube v0.23.0 I got the Heapster addon running within minutes, so things have have considerably improved since @arun-gupta's experience here.. perhaps you would like to close this now?

@r2d4
Copy link
Contributor

r2d4 commented Nov 7, 2017

I'll close this, for anyone seeing anything like this, please open up a new issue. We can always consider caching the enabled addons like we do the control plane now.

@r2d4 r2d4 closed this as completed Nov 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@arun-gupta @vorburger @johnharris85 @r2d4 @aaron-prindle