Open alfredtm opened 2 months ago
I resolved this by setting servicePublishingStrategy.loadBalancer.hostname
to the apiServer's internal service URL.
The certificate-authority-data in bootstrap-kubeconfig is then trusted.
Reopening this issue We are experiencing issues using the apiserver internal service url at a later stage in our deployment.
Ideally we would like to use the external apiserver fqdn in servicePublishingStrategy.loadBalancer.hostname
. But adding apiserver certificate the bootstrap-kubeconfig is no longer trusted.
Is there any way to modify the bootstrap-kubeconfig?
I also found this issue that seems to be the same issue I am experiencing https://issues.redhat.com/browse/OCPBUGS-19067
We have the same issue..
Same issue here, does anyone solved it?
Hello! When adding API server certificate to the HostedCluster
The bootstrap-kubeconfig is no longer trusted
This seems to be a issue when adding new nodes (using kubevirt) to the cluster. They dont register/show up on the HostedCluster.
When not adding certificate to the apiServer the nodes register fine.