S6-Class Project-03

DevOps Easy Learning

​

S6-Class Project-03

DevOps Easy Learning

​

github code

Click here to get the code

​

Problem to solve

• Deploy Espresso Shop microservice application on Kubernetes Cluster using Helm

Main goal from the customer

• Customer name: EXPRESSO INC

EXPRESSO INC business is growing exponentially at the extern that we the headquarter has expressed the need to launch an online shop where millions of customers will be able to shop and post review on different coffee flavor they offer.

To satisfy that need and after a careful selection EXPRESSO INC have picked EK TECH SOFTWARE SOLUTION as their best IT firm to build a robust application that will meet and exceed their expectation.

Requirements from the customer

1- High availability

​

2- zero downtime

​

3- Biweekly deployment

​

4- On demand scalability

Requirements from the Devops Team

• [ ] INSTRUCTIONS
• create a namespace with your prefer name
• Name application with this format [PREFER_NAME]-[APPLICATION_NAME]
• Deploy application with service Type NodePort
• Create a repo in DockerHub with your prefer_name
• write dockerfiles that called all base images with latest tag are avoided also set label with company information
• All Images used will be tag with company repo

​

Requirements from the Devops Team

​

Acceptance Criteria

• Application image is secure
• Image runs as unprivileged user
• Does not listen on privileged (0→1023) ports
• Debug logs are disabled

​

​

Requirements from the Devops Team

​

Helm Chart

• Helm Chart
• Default values result in most-secure install/configuration
• All security-related values are documented
• pods ressource are define
• Applications deploy with app-specific service accounts (not default/shared)
• Service account permissions follow least-privilege principles
• Secrets are used for all sensitive information
• All workloads define appropriate Requests and Limits

​

Requirements from the Devops Team

​

High Availability

• [ ] High Availability
• All workloads have well-defined liveness and readiness probes
• All workloads have well-defined deployment strategy (use rollingUpdate)
• All critical workloads are deployed with multiple replicas
• Workloads requiring persistent volumes are defined by StatefulSets
• Stateful services perform replication using headless services (allowing multiple StatefulSets to coordinate)
• All non-batch workloads have a PodDisruptionBudget defined

​

Application Structure

Frontend

- shop-web

​

API

• shop-product
• shop-reviews-v1
• shop-reviews-v2

​

​

db

• postgres

​

​

​

caching

- Redis

​

Application Structure

FRONTEND:

shop-web

Postgres-HA

API:

shop-reviews-v1

Redis-HA

For session caching

API:

shop-reviews-v2

API:

shop-product

Application Micro-Services

FRONTEND:

shop-web

API:

shop-product

API:

shop-review

Postgres cluster (HA)

Redis (HA)

Application Structure devops stand point

Frontend

- shop-web

​

shop-web

shop-product

shop-reviews-v1

shop-reviews-v2

​

Postgres-HA

Redis-HA

Develop by EK TECH

Develop by Third party

Application Helm Charts (06)

​

shop-web

helm-chart

​

​

shop-product

helm-chart

​

​

​

​

postgres -HA

helm-chart

​

​

​

Redis

helm-chart

​

​

​

shop-reviews

helm-chart

​

​

​

DevOps team service overview�

Application Helm Charts (06)

​

shop-web

helm-chart

​

​

shop-product

helm-chart

​

​

​

​

postgres -HA

helm-chart

​

​

​

Redis

helm-chart

​

​

​

shop-reviews

helm-chart

​

​

​

DevOps Planning�

​

shop-web

helm-chart

​

1. deployment —---- create pod
2. service —--------- expose
3. HPA —--- high available
4. service account
5. PDB

​

DevOps Planning�

​

postgres -HA

helm-chart

​

​

​

1. connection

DevOps Planning�

​

Redis -HA

helm-chart

​

​

​

1. connection

Manage secret with external secret �operator�

ESO link

How to present this project� at your interview�

Accomplishment as team�

Accomplishment individually�

Issues encounter while working� on the project

Take personal notes here