From f626c4e389ce86e7e1419f2d6e6cca130456e405 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Wed, 8 Jul 2020 13:11:23 -0700 Subject: [PATCH] Correct the minimum RKE version for custom CA for S3 --- .../rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md b/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md index 400aee3b3e3..39400b87fbd 100644 --- a/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md +++ b/content/rke/latest/en/etcd-snapshots/one-time-snapshots/_index.md @@ -61,7 +61,7 @@ The `--access-key` and `--secret-key` options are not required if the `etcd` nod ##### Using a custom CA certificate for S3 -_Available as of v2.2.5_ +_Available as of v0.2.0_ The backup snapshot can be stored on a custom `S3` backup like [minio](https://min.io/). If the S3 backend uses a self-signed or custom certificate, provide a custom certificate using the `--s3-endpoint-ca` to connect to the S3 back end.