Skip to content

Commit b484854

Browse files
authored
Correcting etcd backup command for hosted cluster
The command is referencing the wrong CA cert /etc/etcd/tls/client/etcd-client.crt which doesn't exist in the pods and hence the execution fails. The actual CA cert to be used with etcdctl command is /etc/etcd/tls/etcd-ca/ca.crt.
1 parent 3183f7f commit b484854

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

modules/backup-etcd-hosted-cluster.adoc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -33,7 +33,7 @@ $ oc scale deployment -n <hosted_cluster_namespace> --replicas=0 kube-apiserver
3333
+
3434
[source,terminal]
3535
----
36-
$ oc exec -it <etcd_pod_name> -n <hosted_cluster_namespace> -- env ETCDCTL_API=3 /usr/bin/etcdctl --cacert /etc/etcd/tls/client/etcd-client-ca.crt --cert /etc/etcd/tls/client/etcd-client.crt --key /etc/etcd/tls/client/etcd-client.key --endpoints=localhost:2379 snapshot save /var/lib/data/snapshot.db
36+
$ oc exec -it <etcd_pod_name> -n <hosted_cluster_namespace> -- env ETCDCTL_API=3 /usr/bin/etcdctl --cacert /etc/etcd/tls/etcd-ca/ca.crt --cert /etc/etcd/tls/client/etcd-client.crt --key /etc/etcd/tls/client/etcd-client.key --endpoints=localhost:2379 snapshot save /var/lib/data/snapshot.db
3737
----
3838

3939
. To check the snapshot status, use the `exec` command in each etcd container by running the following command:

0 commit comments

Comments
 (0)