From 31783ebd9ac0c77975f7048d91f227841d84001d Mon Sep 17 00:00:00 2001
From: GitHub Actions <actions@github.com>
Date: Wed, 22 Nov 2023 18:33:18 +0000
Subject: [PATCH] Update helm-docs and README.md

---
 charts/posit-chronicle/README.md | 14 +++++---------
 1 file changed, 5 insertions(+), 9 deletions(-)

diff --git a/charts/posit-chronicle/README.md b/charts/posit-chronicle/README.md
index e8b515b1..3b030231 100644
--- a/charts/posit-chronicle/README.md
+++ b/charts/posit-chronicle/README.md
@@ -106,7 +106,7 @@ supported.)
 You can also persist data to AWS S3 instead of (or in addition to) local
 storage:
 
-``` yaml
+```yaml
 config:
   s3Storage:
     enabled: true
@@ -121,22 +121,18 @@ to manage the credentials needed to access S3. In this scenario, once you have
 role](https://docs.aws.amazon.com/eks/latest/userguide/create-service-account-iam-policy-and-role.html),
 you can use this role as an annotation on the existing Service Account:
 
-``` yaml
+```yaml
 serviceaccount:
-  create: false
-  # -- Additional annotations to add to the chronicle-server serviceaccount
-  annotations: {
+  create: true
+  annotations:
     eks.amazonaws.com/role-arn:  arn:aws:iam::123456789000:role/iam-role-name-here
-  }
-  # -- Additional labels to add to the chronicle-server serviceaccount
-  labels: {}
 ```
 
 If you are unable to use IAM Roles for Service Accounts, there are any number of
 alternatives for injecting AWS credentials into a container. As a fallback,
 the S3 storage config allows specifying a profile:
 
-``` yaml
+```yaml
 config:
   s3Storage:
     enabled: true