From 2bd122961b8816b958978df513813ce9a81f8076 Mon Sep 17 00:00:00 2001
From: Catherine Luse <catherine.luse@gmail.com>
Date: Wed, 19 Aug 2020 16:18:09 -0700
Subject: [PATCH] Remove broken image links

---
 .../rke/latest/en/etcd-snapshots/example-scenarios/_index.md  | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/content/rke/latest/en/etcd-snapshots/example-scenarios/_index.md b/content/rke/latest/en/etcd-snapshots/example-scenarios/_index.md
index e57fd3d5871..2cf5ef5aa8b 100644
--- a/content/rke/latest/en/etcd-snapshots/example-scenarios/_index.md
+++ b/content/rke/latest/en/etcd-snapshots/example-scenarios/_index.md
@@ -34,8 +34,6 @@ You can upload this snapshot directly to an S3 backend with the [S3 options]({{<
 $ rke etcd snapshot-save --name snapshot.db --config cluster.yml
 ```
 
-{{< img "/img/rke/rke-etcd-backup.png" "etcd snapshot" >}}
-
 ### 2. Simulate a Node Failure
 
 To simulate the failure, let's power down `node2`.
@@ -133,8 +131,6 @@ Back up the Kubernetes cluster by taking a local snapshot:
 $ rke etcd snapshot-save --name snapshot.db --config cluster.yml
 ```
 
-{{< img "/img/rke/rke-etcd-backup.png" "etcd snapshot" >}}
-
 <a id="store-the-snapshot-externally-rke-prior-to-v0.2.0"></a>
 ### 2. Store the Snapshot Externally