The documentation [0] is not mentioning a mandatory step to encode the provided script to base64

4.1[2-6]

Check the documentation at [0]

    1. Check [0]
    2. The Step #3 in such procedure says "<encoded_etc_find_secondary_device_script>" but there's no mention of a previous step where this is suggested how to be done
    

Customer might be confused on what to place into the following YAML snippet:
            source: data:text/plain;charset=utf-8;base64,<encoded_etc_find_secondary_device_script> 

There should be a Step#3 included in the documentation like:

"Create a base64 encoded string out of the above example script with the following command:
base64 -w0 script.sh"

And subsequenst Steps should be updated with the cascading numbering

[0] https://docs.openshift.com/container-platform/4.16/scalability_and_performance/recommended-performance-scale-practices/recommended-etcd-practices.html#move-etcd-different-disk_recommended-etcd-practices