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

Azure Active Directory

Azure Active directory (AAD) is a Identity as a Service. This is a smaller subset of Active directory. This is not a replacement to active directory at all. Azure active directory provides the identity services to the mobile apps and web apps in Private cloud. These apps may be connected to on-premise applications. So an SSO is enabled for these apps. So Azure active directory has very simple functionality. Create Users, Groups. Map groups to network security groups and provide the authentication to the resources. When you login to Azure portal, right upper corner of the screen has username along with the domain. Domain or tenant or organization are used interchangeably. Management of Users and Groups: Cloud identity (create users manually)  Directory synchronized identifiers (users are synchronized)  Add users Adding a cloud identity users makes the user as Guest When you do directory synchronization on Premise AD Groups are synched up wi...
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