I am trying to provision a kubernetes cluster to vmware.
The Rancher setup is High Availability K3s Kubernetes Cluster.
VMs are created, but from the Nginx Load Balancer I see:
For the one registered agent:
2024/09/27 14:41:03 [crit] 7447#7447: 22577 open() “/var/lib/nginx/tmp/client_body/0000006857” failed (13: Permission denied), client: 192.168.204.40, server: , request: “PUT /api/v1/namespaces/fleet-default/secrets/superkube-controller-b8z4n-shmpq-machine-plan HTTP/1.1”, host: "rancher..*.it"
For the other two VMs:
2024/09/27 14:41:01 [error] 7444#7444: 22514 upstream timed out (110: Operation timed out) while reading upstream, client: 192.168.204.42, server: , request: “GET /api/v1/namespaces/fleet-default/secrets?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dsuperkube-controller-b8z4n-lhkq4-machine-plan&resourceVersion=324592&timeout=6m38s&timeoutSeconds=398&watch=true HTTP/1.1”, upstream: “https://192.168.204.2:443/api/v1/namespaces/fleet-default/secrets?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dsuperkube-controller-b8z4n-lhkq4-machine-plan&resourceVersion=324592&timeout=6m38s&timeoutSeconds=398&watch=true”, host: "rancher...it"
2024/09/27 14:41:01 [error] 7444#7444: 22516 upstream timed out (110: Operation timed out) while reading upstream, client: 192.168.204.13, server: , request: “GET /api/v1/namespaces/fleet-default/secrets?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dsuperkube-controller-b8z4n-mw5nl-machine-plan&resourceVersion=324606&timeout=5m2s&timeoutSeconds=302&watch=true HTTP/1.1”, upstream: “https://192.168.204.2:443/api/v1/namespaces/fleet-default/secrets?allowWatchBookmarks=true&fieldSelector=metadata.name%3Dsuperkube-controller-b8z4n-mw5nl-machine-plan&resourceVersion=324606&timeout=5m2s&timeoutSeconds=302&watch=true”, host: "rancher...it"