You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! When adding API server certificate to the HostedCluster
apiVersion: hypershift.openshift.io/v1beta1
kind: HostedCluster
metadata:
name: test
namespace: test
spec:
configuration:
apiServer:
servingCerts:
namedCertificates:
- servingCertificate:
name: tls-secret
The bootstrap-kubeconfig is no longer trusted
Unable to connect to the server: tls: failed to verify certificate: x509: certificate signed by unknown authority (possibly because of "crypto/rsa: verification error" while trying to verify candidate authority certificate "root-ca")
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.
The text was updated successfully, but these errors were encountered:
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?
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.
The text was updated successfully, but these errors were encountered: