From 20f1ae151f1a3b0ce6fdc07b966d0961b05db2a0 Mon Sep 17 00:00:00 2001
From: Anastasia Alexandrova <anastasia.alexandrova@percona.com>
Date: Tue, 10 Sep 2024 17:57:34 +0200
Subject: [PATCH] PG-918 Updated enable etcd section (#654)

Removed manual dependency installation according to tarball changes

modified:   docs/enable-extensions.md

Signed-off-by: Anastasia Alexadrova <anastasia.alexandrova@percona.com>
---
 docs/enable-extensions.md | 42 ++++++++++++++++-----------------------
 docs/tarball.md           |  8 ++++----
 2 files changed, 21 insertions(+), 29 deletions(-)

diff --git a/docs/enable-extensions.md b/docs/enable-extensions.md
index 4144a3434..bb6753947 100644
--- a/docs/enable-extensions.md
+++ b/docs/enable-extensions.md
@@ -20,31 +20,23 @@ See the configuration guidelines for [Debian and Ubuntu](solutions/ha-setup-apt.
 
 ## etcd
 
-The following steps apply if you [installed etcd  from the tarballs](tarball.md).
-
-1. Install the Python client for `etcd` to resolve dependency issues. Use the following command:
-
-    ```{.bash data-prompt="$"}
-    $ /opt/percona-python3/bin/pip3 install python-etcd
-    ```
-
-2. Create the `etcd.service` file. This file allows `systemd` to start, stop, restart, and manage the `etcd` service. This includes handling dependencies, monitoring the service, and ensuring it runs as expected. 
-
-    ```ini title="/etc/systemd/system/etcd.service"
-    [Unit]
-    After=network.target
-    Description=etcd - highly-available key value store
-
-    [Service]
-    LimitNOFILE=65536
-    Restart=on-failure
-    Type=notify
-    ExecStart=/usr/bin/etcd --config-file /etc/etcd/etcd.conf.yaml
-    User=etcd
-
-    [Install]
-    WantedBy=multi-user.target
-    ```
+If you [installed etcd from binary tarballs](tarball.md), you need to create the `etcd.service` file. This file allows `systemd` to start, stop, restart, and manage the `etcd` service. This includes handling dependencies, monitoring the service, and ensuring it runs as expected. 
+
+```ini title="/etc/systemd/system/etcd.service"
+[Unit]
+After=network.target
+Description=etcd - highly-available key value store
+
+[Service]
+LimitNOFILE=65536
+Restart=on-failure
+Type=notify
+ExecStart=/usr/bin/etcd --config-file /etc/etcd/etcd.conf.yaml
+User=etcd
+
+[Install]
+WantedBy=multi-user.target
+```
 
   
 
diff --git a/docs/tarball.md b/docs/tarball.md
index 647fddcb7..9c6fd5e11 100644
--- a/docs/tarball.md
+++ b/docs/tarball.md
@@ -2,10 +2,10 @@
 
 You can find the binary tarballs on the [Percona website](https://www.percona.com/downloads). Select the desired version from a version dropdown and _All_ from the Select Platform dropdown.
 
-There are the following tarballs available: 
+There are the following tarballs available for both x86-64 and ARM64 architectures: 
 
-* percona-postgresql-{{dockertag}}-ssl1.1-linux-x86_64.tar.gz  - for operating systems that run OpenSSL version 1.x
-* percona-postgresql-{{dockertag}}-ssl3-linux-x86_64.tar.gz - for for operating systems that run OpenSSL version 3.x
+* percona-postgresql-{{dockertag}}-ssl1.1-linux-<architecture>.tar.gz  - for operating systems that run OpenSSL version 1.x
+* percona-postgresql-{{dockertag}}-ssl3-linux-<architecture>.tar.gz - for operating systems that run OpenSSL version 3.x
 
 To check what OpenSSL version you have, run the following command: 
 
@@ -64,7 +64,7 @@ The tarballs include the following components:
 
 ## Procedure
 
-The steps below install the tarballs for OpenSSL 3.x. Use another tarball if your operating system has OpenSSL version 1.x.
+The steps below install the tarballs for OpenSSL 3.x on x86_64 architecture. Use another tarball if your operating system has OpenSSL version 1.x and / or has the ARM64 architecture.
 
 1. Create the directory where you will store the binaries. For example, `/opt/pgdistro`