From 70737b731691376a2dfb118715692ff42b70721f Mon Sep 17 00:00:00 2001 From: davidmirror-ops Date: Fri, 29 Sep 2023 11:06:08 -0500 Subject: [PATCH] Fix JSON indentation in example 2nd try Signed-off-by: davidmirror-ops --- rsts/deployment/deployment/index.rst | 2 +- rsts/deployment/deployment/multicluster.rst | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/rsts/deployment/deployment/index.rst b/rsts/deployment/deployment/index.rst index e253ae480c..bec8cef163 100644 --- a/rsts/deployment/deployment/index.rst +++ b/rsts/deployment/deployment/index.rst @@ -85,7 +85,7 @@ There are three different paths for deploying a Flyte cluster: This option is appropriate if all your compute can `fit on one EKS cluster `__ . As of this writing, a single Flyte cluster can handle more than 13,000 nodes. - Regardless of using single or multiple Kubernetes clusters for Flyte, note that ``FlytePropeller`` -tha main data plane component- can be sharded as well, if scale demands require it. + Regardless of using single or multiple Kubernetes clusters for Flyte, note that ``FlytePropeller`` -the main data plane component- can be sharded as well, if scale demands require it. Helm ==== diff --git a/rsts/deployment/deployment/multicluster.rst b/rsts/deployment/deployment/multicluster.rst index b27ef59a06..5745e93d37 100644 --- a/rsts/deployment/deployment/multicluster.rst +++ b/rsts/deployment/deployment/multicluster.rst @@ -54,9 +54,9 @@ requests successfully, the following environment-specific requirements should be "s3:ListBucket", "s3:PutObject*" ], - "Resource": [ - "arn:aws:s3:::*", - "arn:aws:s3:::*/*" + "Resource": [ + "arn:aws:s3:::*", + "arn:aws:s3:::*/*" ], 2. At least three IAM Roles configured: one for the controlplane components, another for the dataplane