thanos：unmarshal错误：\ n第2行：在类型s3.config中找不到字段加密

发布于 2025-01-21 04:24:05 字数 324 浏览 0 评论 0原文

我也有同样的错误

type: s3
config:
  bucket: monitoring-thanos-dev-metrics #S3 bucket name
  endpoint: s3.ap-southeast-2.amazonaws.com #S3 Regional endpoint
  encryptsse: true

当我掌舵安装最新版本的Prometheus-Community/Kube-prometheus-stack时， thanos-sotre显示了此错误msg：unmarshal错误：\ n行2：type s3.config中未找到字段加密

原文

I have the same error when I helm install the latest version prometheus-community/kube-prometheus-stack with thanos.io v0.25.2 the thanos-storage-config.yaml as following:

type: s3
config:
  bucket: monitoring-thanos-dev-metrics #S3 bucket name
  endpoint: s3.ap-southeast-2.amazonaws.com #S3 Regional endpoint
  encryptsse: true

Then, the thanos-sidecar, thanos-compactor and thanos-sotre has show this error msg: unmarshal errors:\n line 2: field encryptsse not found in type s3.Config

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

蓝眸 2025-01-28 04:24:05

根据 documentation：


type: S3
config:
  bucket: ""
  endpoint: ""
  region: ""
  access_key: ""
  insecure: false
  signature_version2: false
  encrypt_sse: false
  secret_key: ""
  put_user_metadata: {}
  http_config:
    idle_conn_timeout: 0s
    response_header_timeout: 0s
    insecure_skip_verify: false
  trace:
    enable: false
  part_size: 0

看来您似乎有类型密钥名称： encrypt_sse

我有类似的错误，要解决方法，我刚刚删除了 encrypt_sse：false key。

至少您需要为存储桶，端点，access_key和secret_key键提供值。其余的密钥是可选的。

According to the documentation:


type: S3
config:
  bucket: ""
  endpoint: ""
  region: ""
  access_key: ""
  insecure: false
  signature_version2: false
  encrypt_sse: false
  secret_key: ""
  put_user_metadata: {}
  http_config:
    idle_conn_timeout: 0s
    response_header_timeout: 0s
    insecure_skip_verify: false
  trace:
    enable: false
  part_size: 0

it seems you have a type in the key name: encrypt_sse

I had similar errors, to workaround I just removed the encrypt_sse: false key.