Deploy Guest Book App on Kubernetes

This is part five of a series of lab tasks from KodeKloud for Kubernetes level 4. Master blog listing all parts can be seen here. Make sure to follow setup instructions for minikube on your PC.

Problem with Inline Solutions

The Nautilus Application development team has finished development of one of the applications and it is ready for deployment. It is a guestbook application that will be used to manage entries for guests/visitors. As per discussion with the DevOps team, they have finalized the infrastructure that will be deployed on Kubernetes cluster. Below you can find more details about it.

BACK-END TIER

1. Create a deployment named redis-master for Redis master.

   a.) Replicas count should be 1.

   b.) Container name should be master-redis-xfusion and it should use image redis.

   c.) Request resources as CPU should be 100m and Memory should be 100Mi.

   d.) Container port should be redis default port i.e 6379.

    apiVersion: apps/v1
    kind: Deployment
    metadata:
        name: redis-master
    spec:
        replicas: 1
        selector:
            matchLabels:
                app: redis-master
                tier: back-end
        template:
            metadata:
            labels:
                app: redis-master
                tier: back-end
            spec:
                containers:
                    - name: master-redis-xfusion
                    image: redis
                    resources:
                        requests:
                            memory: "100Mi"
                            cpu: "100m"
                    ports:
                        - containerPort: 6379
   

2. Create a service named redis-master for Redis master. Port and targetPort should be Redis default port i.e 6379.

    apiVersion: v1
    kind: Service
    metadata:
        name: redis-master
    spec:
        type: ClusterIP
        selector:
            app: redis-master
            tier: back-end
        ports:
            - port: 6379
            targetPort: 6379
   

3. Create another deployment named redis-slave for Redis slave.

   a.) Replicas count should be 2.

   b.) Container name should be slave-redis-xfusion and it should use gcr.io/google_samples/gb-redisslave:v3 image.

   c.) Requests resources as CPU should be 100m and Memory should be 100Mi.

   d.) Define an environment variable named GET_HOSTS_FROM and its value should be dns.

   e.) Container port should be Redis default port i.e 6379.

    apiVersion: apps/v1
    kind: Deployment
    metadata:
        name: redis-slave
    spec:
        replicas: 2
        selector:
            matchLabels:
                app: redis-slave
                tier: back-end
        template:
            metadata:
                labels:
                    app: redis-slave
                    tier: back-end
            spec:
                containers:
                    - name: slave-redis-xfusion
                      image: gcr.io/google_samples/gb-redisslave:v3
                      resources:
                        requests:
                            memory: "100Mi"
                            cpu: "100m"
                    env:
                        - name: GET_HOSTS_FROM
                        value: dns
                    ports:
                        - containerPort: 6379
   

4. Create another service named redis-slave. It should use Redis default port i.e 6379.

    apiVersion: v1
    kind: Service
    metadata:
        name: redis-slave
    spec:
        type: ClusterIP
        selector:
            app: redis-slave
            tier: back-end
        ports:
            - port: 6379
            targetPort: 6379
   

FRONT END TIER

1. Create a deployment named frontend.

   a.) Replicas count should be 3.

   b.) Container name should be php-redis-xfusion and it should use gcr.io/google-samples/gb-frontend@sha256:cbc8ef4b0a2d0b95965e0e7dc8938c270ea98e34ec9d60ea64b2d5f2df2dfbbf image.

   c.) Request resources as CPU should be 100m and Memory should be 100Mi.

   d.) Define an environment variable named as GET_HOSTS_FROM and its value should be dns.

   e.) Container port should be 80.

    apiVersion: apps/v1
    kind: Deployment
    metadata:
        name: frontend
    spec:
        replicas: 3
        selector:
            matchLabels:
                app: guestbook
                tier: front-end
        template:
            metadata:
                labels:
                    app: guestbook
                    tier: front-end
            spec:
                containers:
                    - name: php-redis-xfusion
                      image: gcr.io/google-samples/gb-frontend@sha256:cbc8ef4b0a2d0b95965e0e7dc8938c270ea98e34ec9d60ea64b2d5f2df2dfbbf
                      resources:
                        requests:
                          memory: "100Mi"
                          cpu: "100m"
                    env:
                        - name: GET_HOSTS_FROM
                          value: dns
                    ports:
                        - containerPort: 80
   

2. Create a service named frontend. Its type should be NodePort, port should be 80 and its nodePort should be 30009.

    apiVersion: v1
    kind: Service
    metadata:
        name: frontend
    spec:
        type: NodePort
        selector:
            app: guestbook
            tier: front-end
        ports:
            - port: 80
              targetPort: 80
              nodePort: 30009
   

Finally, you can check the guestbook app by clicking on App button.

You can use any labels as per your choice.

Note: The kubectl utility on jump_host has been configured to work with the kubernetes cluster.