Fórum Root.cz
Ostatní => Nová témata => Téma založeno: czechsys 21. 08. 2026, 15:29:44
-
Ahoj,
zkousim tuto roli a mam seskladany cely (v 1.35.7, dualstack) rke2 cluster s externi haproxy (api, registrace) a funguje to. Ale cely den se morim i s podporou AI, ze zvoleny (pri instalaci) ingress traefik (daemonset) neni dostupny externe:
# /var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml describe ds rke2-traefik -n kube-system
...
Pods Status: 3 Running / 0 Waiting / 0 Succeeded / 0 Failed
...
Containers:
rke2-traefik:
Image: rancher/hardened-traefik:v3.7.8-build20260717
Ports: 9100/TCP (metrics), 8080/TCP (traefik), 8000/TCP (web), 8443/TCP (websecure)
Host Ports: 0/TCP (metrics), 0/TCP (traefik), 80/TCP (web), 443/TCP (websecure)
Args:
--entryPoints.metrics.address=:9100/tcp
--entryPoints.traefik.address=:8080/tcp
--entryPoints.web.address=:8000/tcp
--entryPoints.websecure.address=:8443/tcp
...
# /var/lib/rancher/rke2/bin/kubectl --kubeconfig /etc/rancher/rke2/rke2.yaml get svc rke2-traefik -n kube-system
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
rke2-traefik ClusterIP 10.43.178.210 <none> 80/TCP,443/TCP 68m
V principu mne AI navedla na pouziti nodePort:
apiVersion: helm.cattle.io/v1
kind: HelmChartConfig
metadata:
name: rke2-traefik
namespace: kube-system
spec:
valuesContent: |-
service:
type: NodePort
ports:
web:
nodePort: 30080
websecure:
nodePort: 30443
resp. v obdobne variante na hostPort. Problem je, ze se mi to sice nakonfiguruje, ale traefik mi bud jako sluzba zmizi ze systemu, pripadne tam zustane, ale stale je ve formatu ClusterIP. Zatim se mi nechce jit pres kube-vip.
Nevi nekdo, co s tim, uz jsem (jako zacatecnik) v koncich. Chci na to prejit z k3s, ktery tu mam jako PoC.
Diky.
-
Možná by pomohlo kouknout sem: https://hostman.com/docs/kubernetes/networking/configuring-public-and-private-services/ (https://hostman.com/docs/kubernetes/networking/configuring-public-and-private-services/)