Hi, this will be because you're on the docker driver, which runs minikube as a docker container. This is good because it is more stable and efficient that running minikube under some kind of VM - but the problem is, you've got 2 network hops to get into the container - one to get past the vm that docker is running under, and then another hop to get to the node port. It's the minikube service command that gets you into that VM. It's a pain, and worse you have to keep that command running, BUT it's worth it - much better than the agony of running minikube standalone. Hope that helps - ps minikube chooses the docker driver by default if docker is running on your system.
You're very kind James and thanks for the sub! Alas I'm too lazy to upload too often, but I hope I'll get round to putting up something soon. All the best!
Thank you for the video! I didn't manage to access the UI without performing port-forwarding, although the service port is 80:30001/TCP what do you think I did missed?
I'm noticing more and more people need to this - I've never worked out what the common factor is, lately I've been theorising it's due to a bug in Docker Desktop on Macs, but I've had others reporting the same problem on a mix of platforms. You've done nothing wrong, the port forward is a good workaround for local network problems. I'd be interested what your platform is though?
Mmm - should be ok, had thousands of people on this course. The grafana is a bit old but should be stable. What does "kubectl get all --all-namespaces" show, is the pod running? Are you on the right port?
Go to the next part, I'm using the discovery of username/password as a way of exploring how to configure with Helm: ruclips.net/video/mcTwkE3jnZc/видео.html
hello, great stuff Richard. I have a question about log in in google kubernetes engine unlike minicube you show on 15:00 ? Any other way than kubectl port-forward?
Somehow the solution in the video did not work for me to expose the service, instead I got it work with:
minikube service monitoring-grafana
Hi, this will be because you're on the docker driver, which runs minikube as a docker container. This is good because it is more stable and efficient that running minikube under some kind of VM - but the problem is, you've got 2 network hops to get into the container - one to get past the vm that docker is running under, and then another hop to get to the node port. It's the minikube service command that gets you into that VM.
It's a pain, and worse you have to keep that command running, BUT it's worth it - much better than the agony of running minikube standalone.
Hope that helps - ps minikube chooses the docker driver by default if docker is running on your system.
@@RichardChesterwoodThanks!!
@@RichardChesterwood would you please stick this comment to the top? Very nice explanation.
@@xiongwe Pinned! I didn't know that feature was available on youtube, thanks for the suggestion!
A true hero to the people. Thanks Richard
You're too kind! Many thanks I hope the videos will be useful! All the best.
Bro you are the best in Helm on youtube
Aw thanks you're very kind! I hated Helm at first which I think is what prompted me to do a full series on it, it's ok when you get used to it!
Straight and simple explanation. Subscribed and looking forward to more such content.
Many thanks! I'm sooooo slooooow at uploading new content though, I'm my own worst enemy. Hopefully something coming soon. All the best!
Excellent course. Not "just facts", but also explains things. Thumbs up, subscribed.
You're very kind James and thanks for the sub! Alas I'm too lazy to upload too often, but I hope I'll get round to putting up something soon. All the best!
Awesome course, thanks!!
Thank you for the video! I didn't manage to access the UI without performing port-forwarding, although the service port is 80:30001/TCP what do you think I did missed?
I'm noticing more and more people need to this - I've never worked out what the common factor is, lately I've been theorising it's due to a bug in Docker Desktop on Macs, but I've had others reporting the same problem on a mix of platforms. You've done nothing wrong, the port forward is a good workaround for local network problems. I'd be interested what your platform is though?
@@RichardChesterwood Hi, thank you for the detailed response, good to know! I'm using Docker for desktop (Windows edition).
@@AfikAfikAfik ah thanks for that, I thought it was just Docker Desktop on Mac, very useful info thanks!
I am running a local kind cluster, how do I get the cluster's ip address. the kind equivalent to minikube ip?
I had to port forward my service to localhost
Richard,
I did everything as in the lecture but my grafana dashboard isn't coming up. loading forever
and known issues with it?
Mmm - should be ok, had thousands of people on this course. The grafana is a bit old but should be stable. What does "kubectl get all --all-namespaces" show, is the pod running? Are you on the right port?
you can use this command "minikube service monitoring-grafana" after edit svc monitoring-grafana
❤
how to login to grafana?
Go to the next part, I'm using the discovery of username/password as a way of exploring how to configure with Helm: ruclips.net/video/mcTwkE3jnZc/видео.html
@@RichardChesterwood ok thank you , btw nice video
hello, great stuff Richard. I have a question about log in in google kubernetes engine unlike minicube you show on 15:00 ? Any other way than kubectl port-forward?
You have a typo in video title :)
Heh well spotted - I did that to see if anyone would spot it, I promise ;-)