wlan-cloud-owls/helm

owls

This Helm chart helps to deploy OpenWIFI Load Simulator (further on refered as Load Simulator) to the Kubernetes clusters. In order to use it you need to have OpenWIFI CloudSDK as it requires connection to multiple services in order to run the simulation. You can find details about installation in assembly chart.

TL;DR;

$ helm install .

Introduction

This chart bootstraps the Load Simulator on a Kubernetes cluster using the Helm package manager.

Installing the Chart

Currently this chart is not assembled in charts archives, so helm-git is required for remote the installation

To install the chart with the release name my-release:

$ helm install --name my-release git+https://github.com/Telecominfraproject/wlan-cloud-owls@helm/owls-0.1.0.tgz?ref=main

The command deploys the Load Simulator on the Kubernetes cluster in the default configuration. The configuration section lists the parameters that can be configured during installation.

Tip

: List all releases using helm list

Uninstalling the Chart

To uninstall/delete the my-release deployment:

$ helm delete my-release

The command removes all the Kubernetes components associated with the chart and deletes the release.

Configuration

The following table lists the configurable parameters of the chart and their default values. If Default value is not listed in the table, please refer to the Values files for details.

Parameter	Type	Description	Default
replicaCount	number	Amount of replicas to be deployed	1
strategyType	string	Application deployment strategy	'Recreate'
nameOverride	string	Override to be used for application deployment
fullnameOverride	string	Override to be used for application deployment (has priority over nameOverride)
images.owls.repository	string	Docker image repository
images.owls.tag	string	Docker image tag	'master'
images.owls.pullPolicy	string	Docker image pull policy	'Always'
services.owls.type	string	OpenWIFI Load Simulator service type	'LoadBalancer'
services.owls.ports.restapi.servicePort	number	REST API endpoint port to be exposed on service	16007
services.owls.ports.restapi.targetPort	number	REST API endpoint port to be targeted by service	16007
services.owls.ports.restapi.protocol	string	REST API endpoint protocol	'TCP'
services.owls.ports.restapiinternal.servicePort	string	Internal REST API endpoint port to be exposed on service	17007
services.owls.ports.restapiinternal.targetPort	number	Internal REST API endpoint port to be targeted by service	17007
services.owls.ports.restapiinternal.protocol	string	Internal REST API endpoint protocol	'TCP'
checks.owls.liveness.httpGet.path	string	Liveness check path to be used	'/'
checks.owls.liveness.httpGet.port	number	Liveness check port to be used (should be pointint to ALB endpoint)	16107
checks.owls.readiness.httpGet.path	string	Readiness check path to be used	'/'
checks.owls.readiness.httpGet.port	number	Readiness check port to be used (should be pointint to ALB endpoint)	16107
ingresses.restapi.enabled	boolean	Defines if REST API endpoint should be exposed via Ingress controller	False
ingresses.restapi.hosts	array	List of hosts for exposed REST API
ingresses.restapi.paths	array	List of paths to be exposed for REST API
volumes.owls	array	Defines list of volumes to be attached to the Load Simulator
persistence.enabled	boolean	Defines if the Load Simulator requires Persistent Volume (required for permanent files storage and SQLite DB if enabled)	True
persistence.accessModes	array	Defines PV access modes
persistence.size	string	Defines PV size	'10Gi'
public_env_variables	hash	Defines list of environment variables to be passed to the Load Simulator
configProperties	hash	Configuration properties that should be passed to the application in owls.properties. May be passed by key in set (i.e. configProperties."rtty\.token")
certs	hash	Defines files (keys and certificates) that should be passed to the Load Simulator (PEM format is adviced to be used) (see volumes.owls on where it is mounted)
certsCAs	hash	Defines files with CAs that should be passed to the Load Simulator (see volumes.owls on where it is mounted)

Specify each parameter using the --set key=value[,key=value] argument to helm install. For example,

$ helm install --name my-release \
  --set replicaCount=1 \
    .

The above command sets that only 1 instance of your app should be running

Alternatively, a YAML file that specifies the values for the parameters can be provided while installing the chart. For example,

$ helm install --name my-release -f values.yaml .

Tip

: You can use the default values.yaml as a base for customization.