consul-template Multi-namespace support for Vault

By setting the namespace in the vault section, we lock ourselves into a single namespace.

Vault clients support namespace as a path prefix Which would be the right way to access secrets in multiple namespaces from a single consul template config.

I use the latest version.

Oct 21 '19 16:10 devlounge

This CT runs as a sidecar container, in kubernetes Version 0.22.0-light

Oct 22 '19 14:10 devlounge

Thanks for the feature request @devlounge

The secret template-function already does a lot, but seems like the place this would have to go if you want to pull secrets from multiple namespaces in a single template. I had thought about making namespaces per-template at one point, but that obviously wouldn't help here. I'll give it some thought.

Dec 18 '19 23:12 eikenb

I have a peculiar but related requirement. I need to auth to one namespace with Kubernetes and then auth to a second namespace with a cert extracted from the first name space. Am I better off just running two instances of consul-template in each pod?

Jan 22 '20 15:01 gabrieljones