This message was deleted.

I have verified that it's enough to add root CA to the pod so it could access GHES by creating the certificate file in the pods directory /etc/ssl/certs and then I added it to the curl command:

curl -v <https://github.myexample.com> --cacert /etc/ssl/certs/rootCA.crt

Would be good to understand where that root CA should be added in K3S so pods could use it.

You might use trust-manager to distribute CAs to namespaces after creating a k8s secret or configmap containing the trusted CA certificate.

Hi, Thank you for your reply! I created a configMap and then attacked it directly in the deployment. That helped to solve an issue.