-
Notifications
You must be signed in to change notification settings - Fork 588
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
Restoring snapshot without pki bundle or rkestate file #1336
Comments
Discussed Solution:
|
The issue here is that the way files are deployed in RKE (by providing the file contents in an environment variable to the container, and echo-ing this variable to a file) will hit a limit of the size of the environment variable in case of 3 nodes with custom certs signed using |
Re-opened as executables are not available for the rcs v1.2.0-rc7 and v1.1.5-rc6. |
Tested using v1.1.5-rc5 .
rke state file is not present in the snapshot zip folder
Tested with v1.2.0-rc7
Performed a restore using custom certs with the below command:
Restore fails with the below error though the pem key
Restore succeeds when the flag --custom-certs cert-dir is not specified. |
Reopening the issue for the following reasons:
But not able to restore using custom certs . |
Tested using v1.1.5-rc7 .
Restore is successful. rkestate file is extracted from the snapshot. Logs below:
|
Re-tested with v1.2.0-rc7 Created a 3 node cluster using custom certs with the steps below
Verified rke state file is present in the snapshot zip folder
Restore is successful. Statefile is extracted from the zip folder
Restore without specifying custom certs is also functional
|
For etcd restore to work correctly the certificates generated originally for the cluster must be present, in rke 0.1 we saved the certs as pki.bundle.tar.gz and in 0.2 we moved to cluster.rkestate file, we expect the state file to be present during the restore, however we also save a copy of the state as a configmap with the name
full-cluster-state
which we might fetch from etcd snapshot directly, the steps to implement this might include:1- restore the etcd snapshot on any node from the cluster.yml
2- fetch the state using etcd client
3- write the state locally on disk
4- continue with restoration
gz#6680
The text was updated successfully, but these errors were encountered: