A retail app that maintains a separate active directory for the user and DB to store product information.

Each Module in this application is decoupled to create a microservice architecture

When Deployed 7 diffrent pods get created in AWS with High availability in diffrent AZ with bastion host to reach private subnets.

To setup max availability the pods are deployed in multi-az environment

In Jenkins setup, for each build all the deployments undergo several layers of load and performance testing

• Service account and role binding can be setup for k8 clusters to ensure security
• Secured TLS endpoints can be implemented
• Encryption at rest and in transit
• ELK stack can be deployed on all the pods to get the logs

=======================APP====================================== APPLICATION IS DOWN FOR MORE FEATURES

http://gwtm.me/

=======================APP=======================================

===============================APP FEATURES================================

• Simple Web APP
• Dockerzied
• KOPS Cluster
• JENKINS - CI/CD Setup
• HELM Installation
• Service Discovery via k8 service account
• Swagger API Documentation
• Session Based Authentication
• DB instances in diffrent pods communicate and persist a single DB
• 6 Instance running in multiple AZs
• Bastion Hosts to reach private instances.
• Hosted in AWS Route 53
• Deployments using docker compose

===============================APP FEATURES====================================

============= Installation GUIDE==============================================

Required Installations

• KOPS
• HELM
• Kubectl
• Docker
• Minkube
• Boto3

Follow README fromInfrastructure AWS

• Create KOPS cluster
• Create Jenkins instance in AWS to setup CI/CD

=============K8s DASHBOARD=============

kubectl apply -f https://raw.githubusercontent.com/kubernetes/dashboard/v2.0.0/aio/deploy/recommended.yaml

cat <<EOF | kubectl apply -f -
apiVersion: v1
kind: ServiceAccount
metadata:
  name: admin-user
  namespace: kubernetes-dashboard
EOF

cat <<EOF | kubectl apply -f -
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: admin-user
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: admin-user
  namespace: kubernetes-dashboard
EOF

kubectl -n kubernetes-dashboard describe secret $(kubectl -n kubernetes-dashboard get secret | grep admin-user | awk '{print $1}')

kubectl proxy

http://localhost:8001/api/v1/namespaces/kubernetes-dashboard/services/https:kubernetes-dashboard:/proxy/

After setting up K8 dashboard, Start deploying the pods into cluster.

move to the frontend directory

helm install frontend ./helm/frontend

move to the order_service directory

helm install order ./helm/order

move to the product_service directory

helm install product ./helm/product

move to the user_service directory

helm install user ./helm/user

helm uninstall frontend
helm uninstall order
helm uninstall product
helm uninstall user

• Install Minkube

• Get kube context

kubectl config get-contexts

• Switch to minkube

kubectl config use-context CONTEXT_NAME

• Start helm installation

• After succesfull deployment, start minikube tunnel to connect to load balancer

minikube tunnel