adamant-kite-4373411/21/2022, 7:30 PM
microscopic-diamond-9474911/22/2022, 8:31 AM
part if it has the right
section. and if the secret was created in the right namespace.
gorgeous-iron-4575511/22/2022, 6:12 PM
So, I fortunately immediately realized my error. I had set the Rancher server service type to LoadBalancer, and mapped the FQDN to the load balancer IP.
After setting the ingress class to nginx, and the service type back to ClusterIP, mapping the FQDN to the ingress controller's IP address, and restarting Rancher server, the certificate chain got finally fixed.
However, now the cluster agent gets stuck to the following point as shown in its log:
"Ignoring ingress because of error while validating ingress class" ingress="cattle-system/rancher" error="ingress does not contain a valid IngressClass"
and finally gets terminated not being able to download the CA root certificate from the /v3/settings/cacerts endpoint.
In my opinion, it is a network connectivity-related issue as the connections between the central station on which Rancher server is running and the peripheral stations whose clusters we want to import is too slow.
Therefore, we may have to abandon the idea of having a central Rancher server for centralized monitoring, and instead deploy a separate Rancher server to each peripheral cluster.
INFO: Using resolv.conf: search cattle-system.svc.mas.local svc.mas.local mas.local nameserver 169.254.25.10 options ndots:5
microscopic-diamond-9474911/24/2022, 7:51 AM
gorgeous-iron-4575511/24/2022, 7:52 AM