Deploying Application using Kubernetes Service with Helm

Deploy and manage IBM HACP EE containerized product components on the local Kubernetes, a container orchestration service to deploy, scale up, scale down and manage containers in the cluster environment.

Prerequisites:

Helm 3.0
kubernetes cluster
kubectl command-line tool to control Kubernetes clusters version ( version >= 1.25.4 )

Download Helm Configuration

Navigate to hacpee_container_readme ➜ Helm-chart ➜ hacpee
Open a terminal window and change the root directory to the above location.

Note: User must make sure that the root directory contains the values.yaml file.

Run your Helm chart

Run below command to deploy the application.

helm install <release-name> .

It takes a few minutes for the service to return a public IP address.

To monitor the progress of the deployment run below command:

kubectl get deployment

Navigate to your application's load balancer in a browser using the <external-ip> to see the sample application.

Find the below details of the helm chart, containing description and default values used. User can change the values based on requirement in values.yaml file.

Parameter	Description	Default value
hod.repository	Repository name of HOD server	hacpee_svr_img
hod.Tag	hod image tag	1.0.0
hod.pullPolicy	image pull policy	IfNotPresent
hacp.repository	repository name of the HACP EE	hacpee_app_img
hacp.Tag	HACP EE image tag	1.0.0
hacp.pullPolicy	image pull policy	IfNotPresent
lm.repository	Repository name of the LicenseManager	hacpee_lm_img
lm.Tag	image tag	1.0.0
lm.pullPolicy	image pull policy	IfNotPresent
redirector.repository	Repository name of Redirector	hacpee_rdr_img
redirector.Tag	image tag	1.0.0
redirector.pullPolicy	image pull policy	IfNotPresent
services.redirector.minport	Port number range that starts from	12173
services.redirector.maxport	Port number range that ends	12178
resources.limits.cpu	cpu limits	0.5
resources.limits.memory	memory limits	512Mi
resources.requests.cpu	to request cpu	0.5
resources.requests.memory	to request memory	512Mi
persistentVolumeClaim.create	to create persistent volume claim	TRUE
persistentVolumeClaim.accessModes	access modes of storage	ReadWriteOnce
persistentVolumeClaim.resources.requests.storage		2Gi
storageClassName	storageClass name based on the environment	""
LicenseAcceptance	to accept the license	"yes"

Upon successful deployment, access IBM HACP EE application components through varied URLs as detailed in the Access Application Post Deployment..

To uninstall the helm chart use the below command:

helm uninstall <release-name>

Verify the deployment using below commands:

List down all the resources
```
kubectl get all 
```
List down all the pods
```
kubectl get pods
```
List down all the services
```
kubectl get svc
```
List down Persistent volume and Persistent volume claim
```
kubectl get pv,pvc
```
List down deployment and replicasets
```
kubectl get deployment
kubectl get rs
```

Note: User must install this helm chart with Ingress service enabled.