owgwui
This Helm chart helps to deploy OpenWIFI Web UI (further on refered as Web UI) to the Kubernetes clusters. It is mainly used in assembly chart as Web UI requires other services as dependencies that are considered in that Helm chart. This chart is purposed to define deployment logic close to the application code itself and define default values that could be overriden during deployment.
TL;DR;
$ helm install .
Introduction
This chart bootstraps the Web UI 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-ucentralgw-ui@helm/owgwui-0.1.0.tgz?ref=main
The command deploys the Web UI 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 |
| nameOverride | string | Override to be used for application deployment | |
| fullnameOverride | string | Override to be used for application deployment (has priority over nameOverride) | |
| images.owgwui.repository | string | Docker image repository | |
| images.owgwui.tag | string | Docker image tag | 'master' |
| images.owgwui.pullPolicy | string | Docker image pull policy | 'Always' |
| services.owgwui.type | string | OpenWIFI Web UI service type | 'ClusterIP' |
| services.owgwui.ports.http.servicePort | number | Websocket endpoint port to be exposed on service | 80 |
| services.owgwui.ports.http.targetPort | number | Websocket endpoint port to be targeted by service | 80 |
| services.owgwui.ports.http.protocol | string | Websocket endpoint protocol | 'TCP' |
| checks.owgwui.liveness.httpGet.path | string | Liveness check path to be used | '/' |
| checks.owgwui.liveness.httpGet.port | number | Liveness check port to be used (should be pointint to ALB endpoint) | http |
| checks.owgwui.readiness.httpGet.path | string | Readiness check path to be used | '/' |
| checks.owgwui.readiness.httpGet.port | number | Readiness check port to be used | http |
| ingresses.default.enabled | boolean | Defines if the Web UI should be exposed via Ingress controller | False |
| ingresses.default.hosts | array | List of hosts for the exposed Web UI | |
| ingresses.default.paths | array | List of paths to be exposed for the Web UI | |
| public_env_variables | hash | Defines list of environment variables to be passed to the Web UI (required for application configuration) |
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.