In the service section at minute 1:16:00 after I changed the context I still didn't see the hellogopher service until I run "kubectl expose deployment hellogopher --type=NodePort --port=8080". I assume that the port should be expose for each namespace or context.
I watched your video a few months ago and I didnt understand a thing now after Ive completed my basic books and now when I am leaning towards dev ops your videos are soo helpful to me I cant put in words. But still if i have to say something that is it took a level of skill and knowledge to understand the depth of your videos, I wish i got a change for a 10 min zoom call there is a lot i want to learn from you. Apart from your video your website also as a revision notes for me and both are valuable for interview preparation and overall understanding of the concepts
I don't understand why, when you get to version 3.0 of the image, the deployment doesn't go back to ready?, how do you debug, yet the code is the same(dashboard: Failed to pull image "xxx/hellogopher:3.0": rpc error: code = Unknown desc = Error response from daemon: pull access denied for xxx/hellogopher, repository does not exist or may require 'docker login': denied: requested access to the resource is denied)
It seems it tries to reach for Docker registry you don't have. Make sure you are inside the Minikube Docker Context both when you build and deploy the Docker Image. There is a difference between the Docker images available on your localhost and inside the Minikube context
Man ..u have a such a great content on docker and Kubernetes, for me its so helpful and this videos should get lot of traction !! One thing I feel that gonna help, is you need to provide a tag like #kubernetes for your video, So that theese tags really help search engine to list theese videos ... !! Hope that helps.
In the service section at minute 1:16:00 after I changed the context I still didn't see the hellogopher service until I run "kubectl expose deployment hellogopher --type=NodePort --port=8080".
I assume that the port should be expose for each namespace or context.
finally!!, thank you so much man!
Great tutorial thanks. It helped me very much.
So good !! thanks a ton buddy .
I am happy you enjoyed bud
You are a miracle!!!
I watched your video a few months ago and I didnt understand a thing now after Ive completed my basic books and now when I am leaning towards dev ops your videos are soo helpful to me I cant put in words. But still if i have to say something that is it took a level of skill and knowledge to understand the depth of your videos, I wish i got a change for a 10 min zoom call there is a lot i want to learn from you. Apart from your video your website also as a revision notes for me and both are valuable for interview preparation and overall understanding of the concepts
I don't understand why, when you get to version 3.0 of the image, the deployment doesn't go back to ready?, how do you debug, yet the code is the same(dashboard: Failed to pull image "xxx/hellogopher:3.0": rpc error: code = Unknown desc = Error response from daemon: pull access denied for xxx/hellogopher, repository does not exist or may require 'docker login': denied: requested access to the resource is denied)
It seems it tries to reach for Docker registry you don't have.
Make sure you are inside the Minikube Docker Context both when you build and deploy the Docker Image.
There is a difference between the Docker images available on your localhost and inside the Minikube context
@@programmingpercy Strange, I had to restart everything and now It goes!
Glad you solved it
Man ..u have a such a great content on docker and Kubernetes, for me its so helpful and this videos should get lot of traction !!
One thing I feel that gonna help, is you need to provide a tag like #kubernetes for your video, So that theese tags really help search engine to list theese videos ... !! Hope that helps.
Wow, thanks for these kind words !!
It really encourages me!
I am glad you enjoyed!
And I'll do my best to spread the videos!:)