最新消息:雨落星辰是一个专注网站SEO优化、网站SEO诊断、搜索引擎研究、网络营销推广、网站策划运营及站长类的自媒体原创博客

How do you protect secrets in the open telemetry contrib configuration? - Stack Overflow

programmeradmin2浏览0评论

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?

发布评论

评论列表(0)

  1. 暂无评论