Add explanatory text to Getting Started section

This provides a bit more detail about exactly what you're getting yourself into with each of the example deployment methods. Signed-off-by: Tim Serong <[email protected]>
aquarist-labs · Aug 2, 2023 · 70f1857 · 70f1857
1 parent 7b0dfe5
commit 70f1857
Showing 1 changed file with 13 additions and 0 deletions.
diff --git a/src/pages/index.js b/src/pages/index.js
@@ -69,6 +69,19 @@ podman run --replace --name=s3gw -it -p 7480:7480 quay.io/s3gw/s3gw:latest
 
 `
         }</CodeBlock>
+        <div><p>Helm is the preferred deployment method, and will automatically use
+          your cluster's default storage class for the backing store.  If you have
+          Longhorn installed already, s3gw will thus use a Longhorn PV.  The above
+          assumes cert-manager and traefik are available, but these and other settings
+          can be overridden via values.yaml.</p>
+          <p>Docker and Podman deployments will use ephemeral storage inside the
+            container by default, so should only be used for testing on a local system.
+          </p>
+          <p>In all the above cases, the default Access Key and Secret Key are
+            set to "test".  Please see <a href="https://s3gw-docs.readthedocs.io/">our documentation</a> for
+            more details on how to configure s3gw.
+          </p>
+        </div>
       </div>
       <div className={`${index.learnMore} ${index.bgPrimary}`}>
         <div className={index.wrap}>