Best Of

Hi @RahulRege,

When in doubt, it always helps to check the documentation

The pod is a wrapper around one or many containers and it creates a network namespace for its container(s) to share.

A pod created with a container is not exposed to the outside world. It is only accessible from the local node so you won't find a port on the local node, but you will be able to access your containerized application thru the pod's IP address.

As opposed to a single container exposed to the outside world thru a random high-port of the local node, a pod is exposed thru another Kubernetes resource - a Service. Specific types of services receive a random high-port on every node in the Kubernetes cluster (the same high-port number reserved on every node), allowing access to a single pod from any node in the cluster and from the outside world.

Regards,
-Chris

Hi,

create is used for new object(s) creation declaratively (from a configuration file) or imperatively ( kubectl create deployment... ,kubectl create service...).

apply offers more flexibility and it is a recommended method for production object updates: it creates new objects if they do not exist from configuration files, it updates existing/live objects from single or multiple configuration files or directories, it helps preserve multiple configuration changes when performed by different sources.

Both commands are described in detail throughout the documentation. Here are a few links:

Kubectl book: https://kubectl.docs.kubernetes.io/

https://kubernetes.io/docs/concepts/overview/object-management-kubectl/overview/

https://kubernetes.io/docs/reference/kubectl/cheatsheet/

https://kubernetes.io/docs/reference/kubectl/overview/

Regards,
-Chris

Hi @furqanbaqai,
You are correct, the statement provided by you is useful for a multi-container pod. That is also mentioned on slide 3.14, right above the statement from the lecture:

If you have more than one container, declare which container

However, for a single-container pod, you can use it just as it is presented in the lecture, without declaring a container name. It works for a multi-container pod as well, but it defaults to the first started container.

Regards,
-Chris