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

https://github.com/splunk/splunk-connect-for-kubernetes/blob/b2f1db705b495e2921f7dd6abfeef03dd40f4b44/helm-chart/splunk-connect-for-kubernetes/charts/splunk-kubernetes-logging/templates/configMap.yaml#L240

My ruby isn't great, but reading this:
`sourcetype ${record.dig("kubernetes", "annotations", "splunk.com/sourcetype") ? "kube:"+record.dig("kubernetes", "annotations", "splunk.com/sourcetype

Perhaps it would be better to install the repositories before trying to install the chart. This way we could find out earlier our course is wrong.

line 237 on chart.py

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

Describe the bug

Version number has to be changed manually.

Expected behavior

Version number changes automatically with each new release

Automation pipeline that keeps version number up to date.

Additional context

From the last Hangout.

I don't know where to start, but with some pointers maybe I can assist :).

Charts from stable repo backed by google apis are being removed and are getting deprecated.
The recommended replacements are bitnami charts

3 of 4 charts are part of the deprecation:
Rabbitmq-ha: https://github.com/helm/charts/tree/master/stable/rabbitmq-ha
Mongodb-replicaset: https://github.com/helm/charts/tree/master/stable/mongodb-