-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Registration agent stopped updating its lease. #59
Comments
you may need to check the |
we got same error after renewing the certificate of api.hubcluster.company.lan (6443) What should be done ? Is it ok to update manually the following secret in every managed cluster ?
|
@abdennour Has the CA of the hub cluster apiserver changed? you can try to update the |
Thanks @zhujian7 ! yep it works! Here steps 1. Get Cert from Hub Cluster #0. Get the new CA certificate
api_cert_secret_name=$(oc get apiserver cluster -ojsonpath='{.spec.servingCerts.namedCertificates[0].servingCertificate.name}')
##
crt_api_base64=$(oc -n openshift-config get secret ${api_cert_secret_name} -ojsonpath='{.data.tls\.crt}')
echo $crt_api_base64
2. Apply new Cert in every managed cluster #1. download current kubeconfig
oc -n open-cluster-management-agent extract secret/bootstrap-hub-kubeconfig --to=.
# Here update kubeconfig and namely "certificate-authority-data" line with the new CA certificate (same value ${crt_api_base64})
#3. Upload new kubeconfig
oc -n open-cluster-management-agent set data secret/bootstrap-hub-kubeconfig --from-file=kubeconfig
# 4. restart agents
oc -n open-cluster-management-agent rollout restart deploy |
The AVAILABLE status started after joining the cluster to the hub is True, the following information:
But after a while, found that the cluster AVAILABLE status automatically changed to Unknown. here is the information:
The text was updated successfully, but these errors were encountered: