* Edit RKE backup and recovery docs
* Edit RKE backup and recovery docs
* Edit RKE restore docs
* Add manual steps to older RKE restore process
* Make example scenario consistent with restore doc
* Remove node3 from table in rke restore scenario
* Remove node3 from both tables in rke restore doc
* Fix typo
* Add numbers to example scenario steps
the bash scripts compiles into a single line which results into something like this:
```
for module in br_netfilter ip6_udp_tunnel ip_set ip_set_hash_ip ip_set_hash_net iptable_filter iptable_nat iptable_mangle iptable_raw nf_conntrack_netlink nf_conntrack nf_conntrack_ipv4 nf_defrag_ipv4 nf_
nat nf_nat_ipv4 nf_nat_masquerade_ipv4 nfnetlink udp_tunnel veth vxlan x_tables xt_addrtype xt_conntrack xt_comment xt_mark xt_multiport xt_nat xt_recent xt_set xt_statistic xt_tcpudp; do if ! lsmod | grep -q $module; then echo "module $m
odule is not present" fi done;
```
to avoid syntax error, extra semicolons fixes the issue
- Condense air gap and normal upgrade instructions for cert-manager down
to a single page. This allowed us to consolidate some repetetive text.
- Add a section explaining cert-manager's API change and the recommended
data migration
- Moved the upgrade instructions out of the cluster administration
section and into the Advanced installation options (not perfect but our
best fit)
- On the pages where we instruct the user to install cert-manger, made a
note and link to our upgrade documentation
Better to be explicit than implicit. There was some confusion on what this was referring to since the section was written with an implicit context that the customer and I were lacking. I've attempted to add the context here.
Problem:
cert-manager is old and will be cut off soon
Solution:
Update docs to include current install instructions and instructions on
how to upgrade cert-manager to the current version