Skip to main content

Kubernetes: 19. Configure Application

Configuring application consists of
  1. Configuring commands and arguments on applications
  2. Configuring environment variables
  3. 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 exits.
What if we want to overwrite the inputs sent to the container, we can do as below


docker run ubuntu-sleeper sleep 10
-> Looks ugly, but does the job, CMD is overwritten with the input values sent to container


Now to send just the input for the sleep command and not overwrite the command itself, 
we can build the image as

FROM ubuntu
ENTRYPOINT ["sleep"]

docker run ubuntu-sleeper 10
-> Entrypoint appends sleep and the input 10 is appended to sleep command

docker run ubuntu-sleeper
-> Error operand is missing!

Update the image with default sleep
FROM ubuntu
ENTRYPOINT ["sleep"]
CMD ["5"]

docker run ubuntu-sleeper
-> This now gets executed with default 5 seconds sleep

docker run --entrypoint sleep2.0 ubuntu-sleeper 10
-> Overwrite the entrypoint command

docker run -e APP_COLOR=pink simple-webapp-color
-> Create a environment variable in the container

Kubernetes Commands
  • The same container can be transferred into a Kubernetes pod
  • Entrypoint in docker will correspond to command in kubernetes
  • Command in docker will correspond to args in kubernetes
  • Note that args is an array

pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
    name: ubuntu-sleeper-pod

spec:
    containers:
    - image: ubuntu-sleeper
      name: ubuntu-sleeper-pod
      command: ["sleep"]
      args: ["5"]

Environment Variables
They can be set in different ways
  • key: value pair
  • ConfigMap
  • Secrets

pod-definition.yaml
apiVersion: v1
kind: Pod
metadata:
    name: ubuntu-sleeper-pod

spec:
    containers:
    - image: ubuntu-sleeper
      name: ubuntu-sleeper-pod
      env:
      - name: APP_COLOR
        value: pink
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: 18. Rollout and Rollback

Deployment When a deployment is created, it triggers a rollout Rollout creates a new revision (version) In the future when new deployment is created,  a new rollout is created The new rollout creates one more "new" version These versions help to keep track of the changes and rollback if necessary Deployment Strategy First strategy is delete and recreate strategy.  Delete all the existing pods and deploy the new updated pods But this comes with application downtime Second strategy and default strategy is Rolling update strategy Kubernetes deletes one pod at a time in the older version and in its place creates a one pod at a time in the newer version Update Strategy Updates can be many things like updating the labels, docker image, replicas etc These are directly updated into the deployment file and the changes are applied When the changes are applied using kubectl apply command, a new rollout and a new revision is created Another way to update the image name is to use the kube
Post a Comment
Read more

Kubernetes: 1. Pod

CREATE NEW POD Every kubernetes pod has 4 root level properties. They are apiVersion kind metadata 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  -> Fil
Post a Comment
Read more