On Thu, Feb 18, 2021 at 10:10 PM Julien Pivotto
wrote:
>
> I would also note that generally we have agreed that it will be possible
> to split the prometheus config in multiple file, currently pending a
> design document.
I think this would only work nicely if your file with the secret
contains a
I would also note that generally we have agreed that it will be possible
to split the prometheus config in multiple file, currently pending a
design document.
On 18 Feb 15:49, Bjoern Rabenstein wrote:
> Hi Prometheans,
>
> Container orchestration platforms like Kubernetes offer secrets
> manageme
I am not against this, but I would like two explicit fields each time, like
we do for bearer tokens. I am in particular against any kind of yaml
trickery to make them fill in one field.
Le jeu. 18 févr. 2021 à 16:16, David Leadbeater a écrit :
> Yes, please.
>
> One implementation that might be
Yes, please.
One implementation that might be nice is if rather than every secret
having to have a matching "secret_file" key alongside it, is if the
secret could be specified as either:
secret: "some-value"
or something like:
secret:
type: file
file: "/etc/my-secrets/..."
Then eve
I think all secrets must be readable from files.
On Thu 18. Feb 2021 at 15:49, Bjoern Rabenstein wrote:
> Hi Prometheans,
>
> Container orchestration platforms like Kubernetes offer secrets
> management. K8s provides those secrets directly to the Kubelet, or via
> environment variables, or as fi
Hi Prometheans,
Container orchestration platforms like Kubernetes offer secrets
management. K8s provides those secrets directly to the Kubelet, or via
environment variables, or as files in a volume that containers can
mount, see
https://kubernetes.io/docs/concepts/configuration/secret/#overview-of
6 matches
Mail list logo
