Installation - Kubernetes

To install PSKnowhow using Kubernetes, it is essential to have three mandatory containers: i) UI, ii) CustomAPI, and iii) MongoDB. Additionally, there are other optional containers, such as jira-processor, devops-processor (including Jenkins, GitHub, GitLab, Bamboo, Bitbucket, Zephyr, Sonar, and TeamCity collectors), azure-board-processor (for Azure Board), and azure-pipeline-repo (for Azure Pipeline and Azure Repo), repotool-django, repotool-knowhow, Postgres and rabbitMQ.
NOTE: Based on specific requirements, you can bring up these respective containers as needed.

customapi with amazoncorretto:17 as base image which handles api request, which runs on 8080 port.
ui with nginx:1.22.1-alpine-slim base image, which proxy-pass to customapi and ui components, which runs on port 80 & 443.
mongodb with mongo:5.0.18 as base image, which stores data and runs on port 27017.
Jira-processor with amazoncorretto:17 base image which is a jira collector.
devops-processor with amazoncorretto:17 base image which collects jenkins, github, gitlab, bamboo, bitbucket, zephyr, sonar, teamcity.
azure-board-processor with amazoncorretto:17 base image and which collects azure board.
azure-pipeline-repo with amazoncorretto:17 as base image which collects azure pipeline and azure repo.
scm-processor-api Its python:3.8 application to calculate KPI metrics of different SCM tools like github, gitlab & Bitbucket.
scm-processor-core Its a python:3.8 application which collects raw data from SCM tools like github, gitlab & Bitbucket and saves it.
scm-processor-postgres: Version 11.1 is used to store repotool related data(Only required when repotool is installed)
scm-processor-rabbitmq Version 3.8-management is a job scheduler user by repotool-knowhow application (Only required when repotool is installed)

The ui container should run on a LoadBalancer service with port 443. The remaining containers should run on the default service i.e ClusterIP.

Architecture diagram Of AWS EKS KnowHOW Kubernetes Cluster

Architecture diagram Of Azure AKS KnowHOW Kubernetes Cluster

Resource requirement:

Customapi : 8GB RAM & 2 CPU
MongoDB : 2GB & 1CPU
UI : 1GB RAM & 1CPU
Jira-processor: 6GB RAM & 2CPU
devops-Processor: 8GB RAM & 2 CPU
Azure-board-Processor: 4GB RAM & 1CPU
Azure-pipeline-repo-Processor: 4GB RAM & 1CPU

Installation Steps

Please ensure you follow the sequence outlined below to complete the process successfully.

Step 1: Create Configmap For pods

Download the Configmap file and add required details

To ensure proper configuration for the pods, please fill in the details in the knowhow-config.yml

Make sure to pass all the environmental key values and configuration details needed for your pods to function correctly.

NOTE: Refer Environmental variable document for in detail explanation check here

Then run

kubectl apply -f knowhow-configmap.yml

Step 2: Deploy MongoDB Pod

When installing Knohow in a Kubernetes (K8s) environment, it is recommended to use cloud-provided services for MongoDB like MongoDB Atlas, Azure Cosmos DB to ensure reliability, scalability, and ease of management. However, for testing or non-production environments, you can also deploy MongoDB as a Kubernetes pod.

To create the MongoDB pod, Download the attached YAML file

This is the YAML file for MongoDB designed specifically for deployment on AWS EKS with an EBS file system for persistent storage. It utilizes static provisioning through Amazon EBS.
This is the YAML file for MongoDB designed specifically for deployment on AWS EKS with an EFS file system for persistent storage. It utilizes static provisioning through Amazon EFS.

Reference: AWS Docs for EKS with EFS

This is the YAML file for MongoDB designed specifically for deployment on AZURE AKS with an Azure Disk file system for persistent storage.

Refference: AZ Docs for PV

Here is a sample YAML file for a MongoDB manifest file that utilizes host path as a volume, although it is recommended for Testing only.

The YAML file specifies the name of the pod, the container image to use, the container port 27017 to expose. and the environmental variables to use

Then apply the configuration by following command

kubectl apply -f mongodb.yaml

Step 3: Deploy customapi Pod

Download the customapi-deploy.yaml manifest file

The YAML file specifies the name of the Deployment, the container image to use, the container port 8080 to expose, and the Environmental variable for MongoDB host to connect to.

Note: Please provide the image tag version in the image place holders in the manifest file.

Then apply the configuration by following command

kubectl apply -f customapi-deploy.yaml

Step 4: Deploy the UI Containers

Deploy the UI containers in the same way as the customapi and MongoDB containers. Here is an YAML file for the ui container:

This sample manifest file uses Load balancer as a Service if you wish not you use LB run this as a Cluster IP and use ingress controller to route traffic to UI pod. Ingress Controller manifest file is attached for reference . The YAML file specifies the name of the pod, the container image to use, and the container port to expose.

Note: Please provide the image tag version in the image place holders in the manifest file Environmental variables

Then apply the configuration by following command

kubectl apply -f ui.yaml

Step 5: Deploy the Processor Containers

Attaching the list of all the processor you may run

Jira-Processor

Note: Please provide the image tag version in the image place holders in the manifest file Environmental variables

Then apply the configuration by following command

kubectl apply -f jira-processor.yaml

Devops-processor

Note: Please provide the image tag version in the image place holders in the manifest file Environmental variables

kubectl apply -f devops-processor.yaml

Azure-board-processor

Note: Please provide the value of all the place holders in the manifest file.

kubectl apply -f azure-board-processor.yaml

Azure-pipeline-repo-Processor

Note: Please provide the value of all the place holders in the manifest file.

kubectl apply -f azure-pipeline-repo.yaml

Step 6 : Installing Authentication and Authorization App

AuthNAuth Backend

The Bellow manifest is for Deployment and service of AuthNauth backend API service

AuhNAuth UI

The Bellow manifest is for Deployment and service of AuthNauth UI service

AuthNAuth PostgresDB

When installing Knohow AuthNauth in a Kubernetes (K8s) environment, it is recommended to use cloud-provided services for Postgres like Azure Cosmos DB for Postgres or Azure Flex server to ensure reliability, scalability, and ease of management. However, for testing or non-production environments, you can also deploy as a Kubernetes pod.

Step 7: Install repo tool

Verify the Deployment

You can verify that the containers are running run the following command:

kubectl get pod

To persist the MongoDB data, you can use your preferred cloud provider's storage solution. Here are the steps you can follow:

Create a persistent volume and claim in your cloud provider's storage solution. This will provide a storage location that will persist even if the MongoDB pod is deleted.
Modify the MongoDB YAML file to use the persistent volume. Here's an example of how to modify the YAML file:

apiVersion: v1
kind: Pod
metadata:
  name: mongodb
spec:
  replicas: 1
  containers:
  - name: mongodb
    image: setup-speedy.tools.publicis.sapient.com/speedy/mongodb:latest
    ports:
    - containerPort: 27017
    volumeMounts:
    - name: mongodb-data
      mountPath: /data/db
  volumes:
  - name: mongodb-data
    persistentVolumeClaim:
      claimName: mongodb-pvc

The volumeMounts section specifies where the persistent volume should be mounted inside the container. The volumes section specifies the name of the volume and where it should be claimed from.

Create the persistent volume claim by running the following command:

kubectl apply -f mongodb-pvc.yaml

Here's an example YAML file for the persistent volume claim:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mongodb-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

The YAML file specifies the name of the persistent volume claim, the access mode, and the requested storage size.

By following these steps, you can persist the MongoDB data in your preferred cloud provider's storage solution.

Upgrade Steps:

If you are upgrading PSknowhow from 7.0.0 to 7.x.x please execute the bellow step else execute step 2

kubectl exec -it <Mongodb Pod name> sh
mongo admin --username="${MONGODB_ADMIN_USER}" --password="${MONGODB_ADMIN_PASS}" --eval "db.shutdownServer()"

Edit the deployment in following order
mongodb
customapi
ui
jira-processor
devops-processor
azure-pipeline-repo
azure-board-processor
by
```
kubectl edit deploy <Deploy name> -o yaml
```
Replace the tag version with the latest version in image section
Check for environmental variable section and add if any new variables are required in current manifest file Refer this docs . And save it.