This message was deleted.
# rancher-setup
a
This message was deleted.
m
Did you create the secret with your private CA and called it tls-ca-additional? Docs for reference. https://ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-references/helm-chart-options#additional-trusted-cas
v
@mysterious-animal-29850 yes, I added the
tls-ca-additional
secret as well, however Rancher pods still won't become ready and I don't see any additional entries in pod logs. I just read a post here where someone said he had full chain in his
tls.crt
so I'll try that next.
👍 1
The problem turned out to be a deny-all network policy applied to cluster which was causing Rancher install to fail to communicate with Kubernetes API, so not even related to certs.
👍 1