Tommy McNeely

@ricoberger THANKS! ... I saw this yesterday, but was in meetings all day ;( ... I need to get some project work completed today, but will jump on testing this...

Looks like this was released a couple days ago? I will hopefully get a chance to try it out :) I am running into an issue finding an environment that...

This is looking OK, so far... NOTE: We already had the kubernetes auth setup... Created the prerequisites: vault_gcp_secret_roleset, kubernetes_service_account, vault_kubernetes_auth_backend_role, vault_policy ... Then the helm chart: ```hcl resource "helm_release" "a0000_vault_secrets_operator"...

One thing we found is that it is a *little* too aggressive on retries... I messed up the path and it looked like it tried ~45 times in just a...

FYI: We are using https://github.com/TJM/vault-secret-helmchart to create our VaultSecret objects through Terraform ;)

> Hi @TJM, thanks for testing. > > 1. Yes the secret will be read twice, when it doesn't already exists. Thats the current behavior of the operator. I will...

Our automated cycle is 60s, but has been running for ~76d, and it has set off disk usage alarms on our ~50GB /var/lib/docker partition. As you say, it uses /root/.cache...

What is the validation process to get a fix for this going? At a minimum, the size limit, maybe some sort of cache cleanup sidecar? or a command line option...

To clarify what @HaveFun83 said... I added the following to the `values:` section for the helmrelease (if you aren't managing helm-operator with a HelmRelease, you may have to unindent by...

This has been open a while I noticed there may be a way to provide extra options to ovftool, is that the recommended way to set these options? (disk.EnableUUID) ?