em/em.0x45.cz
1
0
Fork 0
Code Actions Activity

Fix openQA Helm Chart installation
All checks were successful
Build / build (push) Successful in 19s
Details

Browse Source
This commit is contained in:
Emil Miler
2025-06-19 14:39:36 +02:00
parent c311b67b04
commit 8c9da1d33f
1 changed files with 15 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

29
content/posts/installing-openqa-on-kubernetes-with-helm-charts/index.md
View File

@ -83,12 +83,6 @@ We will be working with the parent chart `openqa`. Since it references the other
## Installing openQA
By default, the openQA WebUI template only exposes ports to the local network inside minikube, which makes the WebUI inaccessible from the host system. We need to add `type: NodePort` to the port specification under `spec:` in `charts/webui/templates/svc.yml`:
```
sed -i '/^[[:space:]]*spec:/a\ type: NodePort' charts/webui/templates/svc.yml
```
We then have to update dependencies and install openQA:
```
@ -101,7 +95,7 @@ We can also list installed releases to confirm that openQA was deployed:
```
$ helm list
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
openqa default 1 2025-06-04 12:39:08.150021755 +0200 CEST deployed openqa-0.1.0
openqa default 1 2025-06-19 12:39:08.150021755 +0200 CEST deployed openqa-0.1.0
```
The minikube dashboard also lists all running pods:
@ -111,16 +105,23 @@ The minikube dashboard also lists all running pods:
### Accessing openQA WebUI
Minikube provides a convenient way to list services and their exposed NodePorts:
Since openQA is confined to its own network within minikube, it is not directly accessible from the host system. Below are the services running inside minikube:
```
$ minikube service openqa-webui --url
http://192.168.49.2:30765
http://192.168.49.2:30134
http://192.168.49.2:30333
http://192.168.49.2:31258
$ kubectl get services
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
db ClusterIP 10.103.192.20 <none> 5432/TCP 6m34s
db-hl ClusterIP None <none> 5432/TCP 6m34s
kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 174m
openqa-webui ClusterIP 10.104.24.71 <none> 9526/TCP,9527/TCP,9528/TCP,9529/TCP 6m34s
```
The openQA WebUI is running on port *30765*, which is now accessible directly from your browser.
First, we need to create a proxy within the minikube network:
```
minikube tunnel
```
The openQA WebUI is running at `10.104.24.71` on port `9526` and is now accessible directly from the browser.
![openQA Dashboard](openqa-dashboard.png)