Docs: Geo Advanced setup from existing primary should mention that the CNH values need to be base64-encoded
In the Geo advanced docs, it mentions adding the secrets manually to the CNH installation, but it looks like these values should be base64 encoded. Without encoding them, GET fails with "invalid base64 encoding" errors when attempting to create the Kubernetes Secrets objects.
Something like this would help point this out:
diff --git a/docs/geo/geo_advanced.md b/docs/geo/geo_advanced.md
index bd5bd65b..c61fed9d 100644
--- a/docs/geo/geo_advanced.md
+++ b/docs/geo/geo_advanced.md
@@ -204,6 +204,8 @@ The below settings are only required when migrating to a Cloud Native Hybrid ins
- `geo_primary_ssh_host_keys` - A dictionary of SSH host keys and values to be used as the Chart's SSH Host Keys secret.
- `geo_primary_registry_key` - A dictionary of the registry `.crt` and `.pem` files to be used as the Chart's Registry authentication certificate, only required if using the Container Registry.
+:information_source: Note that these values should be base-64 encoded representations of the file contents. For example: `cat ssh_host_ecdsa_key | base64`
+
:exclamation: These are sensitive variables. It's strongly recommended taking appropriate precautions to avoid leaking secrets such as using [secret managers or environment variables](../environment_configure.md#sensitive-variable-handling-in-ansible).
```yml