From 8c9da1d33f31e03b54e69a6e057f23854031b147 Mon Sep 17 00:00:00 2001
From: Emil Miler <em@0x45.cz>
Date: Thu, 19 Jun 2025 14:39:36 +0200
Subject: [PATCH] Fix openQA Helm Chart installation

---
 .../index.md                                  | 29 ++++++++++---------
 1 file changed, 15 insertions(+), 14 deletions(-)

diff --git a/content/posts/installing-openqa-on-kubernetes-with-helm-charts/index.md b/content/posts/installing-openqa-on-kubernetes-with-helm-charts/index.md
index ee1a5d3..27743fe 100644
--- a/content/posts/installing-openqa-on-kubernetes-with-helm-charts/index.md
+++ b/content/posts/installing-openqa-on-kubernetes-with-helm-charts/index.md
@@ -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)