fix(k8s): correct Gateway API configuration for Traefik (#48)

- Enable kubernetesGateway provider in Traefik configuration
- Update Gateway to use 'traefik' GatewayClass (auto-created by Traefik)
- Use correct entryPoint ports (8000 for HTTP, 8443 for HTTPS)
- Remove custom GatewayClass (Traefik creates its own)

The Gateway API now works correctly with the K3s development environment.
Test with: curl -H "Host: test-app.localhost" http://localhost:8080

Co-authored-by: rafaelrsantosti <11065120+rafaelrsantosti@users.noreply.github.com>

Author: rafaelrsantosti

docker/manifests/01-gateway.yaml

@@ -1,27 +1,20 @@
 apiVersion: gateway.networking.k8s.io/v1
-kind: GatewayClass
-metadata:
-  name: gatewayclass
-spec:
-  controllerName: traefik.io/gateway-controller
----
-apiVersion: gateway.networking.k8s.io/v1
 kind: Gateway
 metadata:
   name: gateway
   namespace: kube-system
 spec:
-  gatewayClassName: gatewayclass
+  gatewayClassName: traefik
   listeners:
-    - name: http
+    - name: web
       protocol: HTTP
-      port: 80
+      port: 8000
       allowedRoutes:
         namespaces:
           from: All
-    - name: https
+    - name: websecure
       protocol: HTTPS
-      port: 443
+      port: 8443
       allowedRoutes:
         namespaces:
           from: All

docker/manifests/traefik.yaml

@@ -25,6 +25,8 @@ spec:
       kubernetesIngress:
         publishedService:
           enabled: true
+      kubernetesGateway:
+        enabled: true
     priorityClassName: "system-cluster-critical"
     image:
       repository: "rancher/mirrored-library-traefik"