Score:0

How to prevent External Secrets from modifying existing k8s secrets if it's having difficulty with the secret store

cn flag

We're using the latest external secrets operator from external-secrets.io to get secrets from Vault and inject them into kubernetes. We had a situation where a Vault KV engine was upgraded from v1 to v2. This caused External Secrets to no longer be able to find the secrets in Vault, and as a result it replaced the values of all the k8s secrets with Null values (""). Needless to say, this isn't the type of behavior we necessarily want. Is there a way to prevent this from happening - ie. if ESO is having difficulty with Vault, can it be configured to avoid modifying existing k8s secrets?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.