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
It happens every so often that more time passes between cluster registration in Lieutenant and the actual bootstrapping of Steward so that the bootstrap token already expired. Or the same cluster needs to be replaced again with the same cluster ID, but the bootstrap token has already been used.
Expose a functionality in the API to reset the cluster bootstrap token to be valid (again).
Manual process, directly on the Kubernetes API object:
It boils down to remove the field .status.bootstrapToken from the Cluster object, the bootstrap token gets recreated by the Lieutenant Operator automatically again.
Alternatives
Only document how to reset the bootstrap token, not exposing any automation for it.
The text was updated successfully, but these errors were encountered:
Context
It happens every so often that more time passes between cluster registration in Lieutenant and the actual bootstrapping of Steward so that the bootstrap token already expired. Or the same cluster needs to be replaced again with the same cluster ID, but the bootstrap token has already been used.
Expose a functionality in the API to reset the cluster bootstrap token to be valid (again).
Manual process, directly on the Kubernetes API object:
It boils down to remove the field
.status.bootstrapToken
from theCluster
object, the bootstrap token gets recreated by the Lieutenant Operator automatically again.Alternatives
Only document how to reset the bootstrap token, not exposing any automation for it.
The text was updated successfully, but these errors were encountered: