chore: update to use metallb

Signed-off-by: Valery Piashchynski <piashchynski.valery@gmail.com>

Author: rustatian

README.md

@@ -65,7 +65,7 @@ helm upgrade --install roadrunner ./deploy/charts/roadrunner -n roadrunner --cre
 ### Argo CD sync
 
 1. Edit `deploy/argocd/application.yaml` (`repoURL`, `targetRevision`) if needed.
-2. Edit `deploy/argocd/values.yaml` (image, worker command, gateway hostnames/class, metrics settings).
+2. Edit `deploy/argocd/values.yaml` (image, worker command, exposure mode, metrics settings).
 3. Apply:
 
 ```bash
@@ -75,8 +75,32 @@ kubectl apply -f deploy/argocd/application.yaml
 The Argo CD example values are preconfigured for:
 
 - image: `ghcr.io/roadrunner-server/rr-php-worker-example:latest`
-- Gateway hostname: `roadrunner.home.arpa`
-- GatewayClass: `cilium`
+- Service type: `LoadBalancer` (MetalLB-friendly)
+- `gateway.enabled: false`
+- `ingress.enabled: false`
+
+### MetalLB profile (no Gateway controller)
+
+If your cluster uses MetalLB and does not run a Gateway API controller, use:
+
+```yaml
+service:
+  type: LoadBalancer
+
+gateway:
+  enabled: false
+
+ingress:
+  enabled: false
+```
+
+Then sync ArgoCD and check:
+
+```bash
+kubectl -n roadrunner get svc roadrunner -w
+curl -sS http://<external-ip>/
+curl -sS http://<external-ip>/health
+```
 
 ### Probe and metrics defaults
 
@@ -94,3 +118,9 @@ The chart mounts `/etc/rr/.rr.yaml` from a ConfigMap by default. This can overri
 - Default `GatewayClass` is `cilium`.
 - The chart renders `Gateway` and `HTTPRoute` by default.
 - Ingress remains available as fallback (`ingress.enabled=true` with `gateway.enabled=false`).
+
+### Troubleshooting
+
+- ArgoCD `Progressing` with health details `Waiting for controller` means Gateway resources are enabled but no Gateway controller is reconciling them.
+- `kubectl get gatewayclass` returning no resources indicates Gateway API objects will not become `Healthy` until a controller/GatewayClass is installed.
+- If ArgoCD still applies old values after local edits, ensure changes are committed and pushed to the revision ArgoCD tracks.

deploy/argocd/README.md

@@ -11,7 +11,7 @@ This folder provides a ready-to-sync Argo CD application for the in-repo Helm ch
 
 1. Review and edit `values.yaml`:
 - Set your application image and worker command.
-- Adjust Gateway API hostnames and `gateway.className` (default: `cilium`).
+- Choose exposure mode (Gateway API, Ingress, or MetalLB LoadBalancer service).
 - Enable or disable metrics and ServiceMonitor.
 
 2. If you deploy from a fork or branch, update `repoURL` and `targetRevision` in `application.yaml`.
@@ -27,18 +27,43 @@ kubectl apply -f deploy/argocd/application.yaml
 5. Verify on your homelab:
 
 ```bash
-curl -sS http://roadrunner.home.arpa/
-curl -sS http://roadrunner.home.arpa/health
+kubectl -n roadrunner get svc roadrunner -w
+curl -sS http://<external-ip>/
+curl -sS http://<external-ip>/health
 ```
 
-If your cluster does not expose `GatewayClass` `cilium`, either install/configure Gateway API support or switch to ingress compatibility mode (`gateway.enabled=false`, `ingress.enabled=true`).
+If you prefer Gateway API mode, set `gateway.enabled=true`, configure hostnames, and ensure a controller/GatewayClass (for example `cilium`) exists.
+
+## MetalLB Mode
+
+Use this mode when your cluster has MetalLB but no Gateway API controller:
+
+```yaml
+service:
+  type: LoadBalancer
+
+gateway:
+  enabled: false
+
+ingress:
+  enabled: false
+```
+
+After sync:
+
+```bash
+kubectl -n roadrunner get svc roadrunner -w
+curl -sS http://<external-ip>/
+curl -sS http://<external-ip>/health
+```
 
 ## Default Example Values
 
 - `image.repository`: `ghcr.io/roadrunner-server/rr-php-worker-example`
 - `image.tag`: `latest`
-- `gateway.className`: `cilium`
-- `gateway.route.hostnames`: `roadrunner.home.arpa`
+- `service.type`: `LoadBalancer`
+- `gateway.enabled`: `false`
+- `ingress.enabled`: `false`
 
 ## Notes
 
@@ -57,3 +82,4 @@ rr serve -c /etc/rr/.rr.yaml -w /app
 - Gateway API is the default north-south exposure model.
 - This requires Gateway API CRDs and a Gateway controller (for example, Cilium Gateway API support).
 - Ingress is still available as a compatibility fallback (`ingress.enabled=true` and `gateway.enabled=false`).
+- If ArgoCD app health remains `Progressing` with message `Waiting for controller`, check whether `Gateway`/`HTTPRoute` are still rendered and whether any `GatewayClass` exists.

deploy/argocd/values.yaml

@@ -45,8 +45,11 @@ resources:
     cpu: 1000m
     memory: 512Mi
 
+service:
+  type: LoadBalancer
+
 gateway:
-  enabled: true
+  enabled: false
   create: true
   className: cilium
   listeners: