[ Kube 6 ] Running Docker Containers in Kubernetes Cluster

Running Docker Containers in Kubernetes Cluster.

In this video, I will show you how to run simple containers quickly and easily inside Kubernetes Cluster.

For any questions/issues/feedback, please leave me a comment and I will get back to you as quickly as I can. If you liked this video, please share it with your friends and don't forget to subscribe to my channel.

Hope you found this video informative and useful. Thanks for watching.

If you wish to support me:

#kubernetes #k8s #justmekubernetes #docker #learnkubernetes

[sreerang]

Crisp and Clean, to the point both install and uninstall options highly unique.

[wisdom]

the content straight forward meant for initial user who want to learn kubernetes, Thanks Buddy.

[rohanrana]

Hey venkat,
Thanks man, really appreciate the hard work and effort, Its like you are sitting beside me and teaching the stuff.
:)

[rpiisenh]

Thanks a lot. It works fine. I have been able to run nginx using kind

[heygokul]

thanks creating the videos, simple and very informative.

[systemadministrator]

Thank you for you videos.
I did like you, but I get:
The connection to the server localhost:8080 was refused - did you specify the right host or port?

[SNEM]

*Clicks on video*
*Finds out that this is a "Just me and Opensource" video*
*Presses like*
*Starts actually watching the video*

[mohannagandlla]

Hi the tutorial is cool but I have one query that is I have created one master and two workers cluster creation is successful and I have deploy the Prometheus but coming to UI expose the service is cluster IP I change it to loadbalencer it's not working and I have used port forward also not working it's shows like sevice not found

[axhackintosh]

I have a silly question

What is the difference between "kubectl apply -f file.yaml" and “kubectl create -f file" ?

[MrNiceseb]

kubectl cluster-info and get nodes work from my controlling machine, but only if I am sudo su. How to use without root?

[rafau]

You should describe more what commands are doing - why NodePort why kubectl *-rm* etc. other than that nice vid

[bhanukumar]

Hi, great videos first. i have a doubt, ..while doing port forwarding for nginx container, you provided 8080 for host machine. is it virtual machine port or the physical base machine port (where you are running virtual machines)? or both or same? or we are skipping virtual machine, as we are interacting to the kubernetes from the physical base machine. ?

[MrNiceseb]

instead of working with images already there, could you show k8s run but from docker hub thanks

[SandeepGupta-uepy]

Hi sir while creating ngnix container
getting error
kubectl run ngnix --image ngnix




pod/ngnix 0/1 ImagePullBackOff 0 4m3s 192.168.136.67 kworker2.example.com <none>
one>

[zwetschgaderdle]

I am running a cluster on different vms on different hosts. When I do the port forwarding and try to access the nginx server, it only works on that same vm.
example: on knode1: curl -XGET 127.0.0.1:8081 works,
but if I do knode2: curl -XGET 10.100.11.152:8081 I get connection refused

[subodhgholap]

Hello Venkat, Thanks for Videos on kubernetes. I need to to access nginx 80 port on NodePort 80 but it is showing that it was having some range. can you please explain how to change to nodePort to 80 ?

[miskeenhazeemmohamedhijas]

Hi, I want ask you that is it possible to run multiple container in same pod with same image like nginx. i am getting errors

[msamonte]

Hello, thanks for making these videos. They are really helpful!
I just started learning K8s few weeks ago.
I ran into a different result when trying to delete the deployment.
I followed your instructions... all the way from your first K8s video.

Here's what I got:
$ kubectl run myshell -it --image busybox -- sh
Error from server (AlreadyExists): replicationcontrollers "myshell" already exists
$ kubectl delete deploy myshell
Error from server (NotFound): the server could not find the requested resource
$ kubectl get deploy
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
calico-kube-controllers 1 1 1 1 19d
coredns 2 2 2 2 19d

It was also weird how I was able to delete the docker images and containers on worker1 but not on worker2. The pods kept coming back on worker2. So then I went back to the actual error message and found out about some commands I used to solve my problem.

$ kubectl get rc
NAME DESIRED CURRENT READY AGE
myshell 1 1 1 3d
nginx 1 1 1 3d
$ kubectl delete rc myshell
replicationcontroller "myshell" deleted
$ kubectl delete rc nginx
replicationcontroller "nginx" deleted
'$ kubectl get rc
No resources found.

After that, I was able to permanently delete the containers and images on worker2.
Would you know why I got that error message as opposed to what you got?
Thanks again.

[Nimitali]

Hi Venkat, Thanks for the functionality works seamlessly....but one question in the browser i have to type in node1IP and NodePort which works well but when i type in kworker1:NodePort it does not work...Checked the config in /etc/hosts of master and worker nodes and everything is in place....can you let me know the reason of the same...

[fahadrao]

Anything you have showed in this video will be run as same on Ubuntu?? Or not