Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

What would you like to be added:

Document experience we have seen with various log rotation size/frequency settings and how rotate_wait or refresh_interval may help.

Why is this needed:

To help users validate the upper limit of a single collector and review some deployment changes that can be made t

The kube context needs to be checked.

Specifying --set 'hydra-maester.enabledNamespaces={<mynamespace>} produces a broken definition:
error validating data: ValidationError(RoleBinding.roleRef): unknown field "namespace" in io.k8s.api.rbac.v1.RoleRef; if you choose to ignore these errors, turn validation off with --validate=false

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Checked that your issue isn't already filled: https

Somewhat similar to StackStorm/st2#4762 (comment), creating a diagram describing complex K8s infrastructure behind the default stackstorm-ha that helm deployment provides would be a nice addition.

If anyone wants to play with it and put it together as a nice image, - contributions are welcome!