Skip to main content

Kubernetes: 1. Pod

CREATE NEW POD

Every kubernetes pod has 4 root level properties. They are

  1. apiVersion
  2. kind
  3. metadata
  4. spec

For a pod these are as below.
metadata -> Data about the Pod, note that we cannot have anything we want here. Only allowed values have to be used.
metadata -> labels. This can be any key:value pairs, think of this as custom properties. 
spec -> containers -> "- name". This is list, because we can have multiple containers running in a pod. "-" Indicates its a list

pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
  name: myapp-pod
  labels:
    app: myapp
    location: IN

spec:
  containers:
  - name: nginx-container
    image: nginx
  - name: backend-db
    image: redis

The easy way to create a pod is using kubectl run
kubectl run <pod-name> --image=<image-name>


DELETE A POD
Get the list of pods running and then delete the pod
kubectl get pods

kubectl delete pod <pod-name

kubectl delete -f <pod-definition-file> -f 
-> Filename, directory, or URL to a file containing the resource to delete.


UPDATE A POD
There are two ways to update a pod
  1. kubectl edit pod <pod-name> -> You will observe that full definition of pod as created by kubernetes will be shown
    With this the changes are automatically applied to the pod and the pod is restarted
  2. Directly update the YAML file and use kubectl apply command
    With this the changes are updated only after running the kubectl apply command

Note that Kubernetes does not allow many properties of the pod to be changed once created. Below specifications are NOT ALLOWED to be changed.
  • spec.containers[*].image
  • spec.initContainers[*].image
  • spec.activeDeadlineSeconds
  • spec.tolerations

But if you need to make certain changes, then there are 2 options
  1. Use kubectl edit pod
  2. Extract pod output in YAML format and make changes
  • With kubectl edit pod, kubernetes gives an error that the changes cannot be made
  • But at the same time kubernetes makes a copy of the changes under /tmp directory. It gives the full path for the definition file
  • Simply delete the existing pod and recreate the new pod using the updated definition file
  • With second option, get the pod output in yaml format by using "-o yaml" option
  • Update the yaml file with new changes
  • Delete the old pod and create the new pod with the updated yaml file
  • As we can see both the options are bit painful, that is why it is better to create a deployment file
  • Kubernetes allow changes to the deployment definition
  • This is because kubernetes deletes all the pod templates defined in deployment and re-creates the pod everytime there is a change to deployment definition

kubectl edit pod <pod-name>

kubectl apply -f <pod-definition-yaml-file-name>

kubectl get pod webapp -o yaml > my-new-pod.yaml

Labels:

Comments

Post a Comment

Popular posts from this blog

Kubernetes: 15. Multiple Schedulers

Custom Scheduler Kubernetes allows to create custom schedulers There can be multiple schedulers running at a same time apart from the default scheduler or A custom scheduler can replace the default kube-scheduler to become the default one So a few pods that requires additional checks apart from taints and toleration, node affinity can go through the custom scheduler before getting scheduled on the node Whereas the rest of the pods can go through the default kube-scheduler Create Custom Scheduler We can either download the kube-scheduler and run it as a service or alternatively create it using a static pod Below here we are downloading the binaries to run it The property scheduler-name is used to define the name of the scheduler, if not set then it will be defaulted to default-scheduler For your custom schedulers, update this property name to set a custom name for your scheduler For Static pods, the name can be updated directly in the pod-definition file Use kubectl create -f <pod-de...
Post a Comment
Read more

Kubernetes: 19. Configure Application

Configuring application consists of Configuring commands and arguments on applications Configuring environment variables Configuring secrets Docker Commands docker run ubuntu  -> Runs ubuntu container and exit, container CMD is set to [bash], so the container quitely exits docker run ubuntu echo "Hello World" -> Runs ubuntu container, prints "Hello World" exits quitely. To update the default settings, create your own image from the base image lets call this ubuntu-sleeper image FROM ubuntu CMD sleep 5 CMD can also be mentioned in the JSON format like CMD ["sleep", "5"] Note that with JSON format the first element should always be the command to execute,  for eg, it CANNOT be ["sleep 5"] Run build the new ubuntu-sleeper image and run the new image docker build -t ubuntu-sleeper .  -> Build the image docker run ubuntu-sleeper -> Run the new image So the new image will launch ubuntu container, sleep for 5 seconds and quitely ex...
Post a Comment
Read more

Kubernetes: 8. Labels & Selectors

Labels Labels are a way of grouping the objects While Kubernetes understands the objects it create, it is easier to identify the objects by using custom labels With labels you group the objects by types (Pods, Services, ReplicaSet etc) or by Applications For a pod, labels are defined under the metadata section Selectors Selectors are used to filter the objects using labels defined on them Using kubectl and selector pods can be listed by filtering on the labels attached to them If a Selector has multiple labels, they are understood as logical AND, which means pods must match all labels. pod-definition.yaml apiVersion: v1 kind: Pod metadata:      name: myapp-pod      labels:           app: myapp           location: IN spec:      containers:      - name: nginx-container        image: nginx kubectl get pods ...
Post a Comment
Read more