<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Using the ETCD Helper module on</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/</link><description>Recent content in Using the ETCD Helper module on</description><generator>Hugo -- gohugo.io</generator><lastBuildDate>Tue, 06 Oct 2020 08:48:23 +0000</lastBuildDate><atom:link href="https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/index.xml" rel="self" type="application/rss+xml"/><item><title>Install module</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/about/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/about/</guid><description>Restoring the ETCD cluster using the etcd-helper module is only possible in a highly available (HA) cluster:
if the ETCD cluster node is unavailable; when the IP address of the Control Plane node changes; when changing the IP addresses of all Control Plane nodes. To start working with the module:
Install the etcd-helper package containing the edtcdctl, etcdutl, etcdhelper utilities. Command yum install etcdhelper The etcd-helper module will be loaded into /usr/local/bin.</description></item><item><title>Recovering an unavailable ETCD cluster node</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/unavailable-node/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/unavailable-node/</guid><description>Before proceeding with recovery, install module etcd-helper.
If the IP address and name of the API server have not changed, but the data on the Control Plane node is corrupted, recreate the node in the ETCD cluster by running the etcdhelper rejoin command.
Command /usr/local/bin/etcdhelper rejoin Screenshot Please note! If the ETCD container on the node is in Running status, then the etcdhelper rejoin command cannot be executed.
As a result of executing the command, the following will happen:</description></item><item><title>Recovery when the IP address of a Control Plane node changes</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/ip-change/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/ip-change/</guid><description>Before proceeding with recovery, install module etcd-helper.
If the IP address of one of the Control Plane nodes is changed, then restore the ETCD cluster using the etcdhelper ip command.
Example command /usr/local/bin/etcdhelper ip --nodeip=ENTER-NEW-NODE-IP-ADDRESS Screenshot As a result of the command, the following will be executed:
Backup manifests and certificates. Changed host IP address in manifests. Removed ETCD certificates, with the exception of the CA certificate. Certificates have been generated, including for the API server.</description></item><item><title>Recovery when the IP addresses of all Control Plane nodes change</title><link>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/allip-change/</link><pubDate>Mon, 16 Nov 2020 13:59:39 +0100</pubDate><guid>https://docs.shturval.tech/2.13/en/cluster-admin/howto/etcd/backup/etcd-helper/allip-change/</guid><description>Before proceeding with recovery, install module etcd-helper.
To restore the functionality of the etcd cluster if the IP addresses on all Control Plane nodes change, follow these steps:
On the first Control Plane node, run the command to prepare the configuration using your parameter values: Example command /usr/local/bin/etcdhelper prepare --nodeip=ENTER-NEW-NODE-IP-ADDRESS Add the --force-new-cluster option to the /etc/kubernetes/manifests/etcd.yaml manifest.
Reboot the first Control Plane node.
Edit the node entry in the etcd cluster.</description></item></channel></rss>