admin管理员组

文章数量:1241128

The open telemetry collectory contrib project has a k8s example to configure the exporter that looks like this

exporters:
  datadog:
    api:
      key: "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" # Change this to your Datadog API key
      site: datadoghq # Change this to your site if not using the default

But that API key is a secret and this example is for a configmap. How can I configure the exporter to pull the API key from a secret instead of being hard coded into a config map?

Some other tools would allow you to specify a file, or a secret name instead such as:

exporters:
  datadog:
    api:
      key-file: /path/to/mounted/secret
      site: datadoghq

or

exporters:
  datadog:
    api:
      key-secret-name: name-of-kubernetes-secret-resource-in-same-namespace
      site: datadoghq

Or how are others protecting their API key?

本文标签： How do you protect secrets in the open telemetry contrib configurationStack Overflow

版权声明：本文标题：How do you protect secrets in the open telemetry contrib configuration? - Stack Overflow 内容由网友自发贡献，该文观点仅代表作者本人， 转载请联系作者并注明出处：http://www.betaflare.com/web/1740054157a2222284.html， 本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容，一经查实，本站将立刻删除。