Comment on page

Thanos Upgrade

Kubecost v1.67.0+ uses Thanos 0.15.0. If you're upgrading to Kubecost v1.67.0+ from an older version and using Thanos, with AWS S3 as your backing storage for Thanos, you'll need to make a small change to your Thanos Secret in order to bump the Thanos version to 0.15.0 before you upgrade Kubecost.
Thanos 0.15.0 has over 10x performance improvements, so this is recommended.
Your values-thanos.yaml needs to be updated to the new defaults here. The PR bumps the image version, adds the query-frontend component, and increases concurrency.
This is simplified if you're using our default values-thanos.yaml, which has the new configs already.
For the Thanos Secret you're using, the encrypt-sse line needs to be removed. Everything else should stay the same.
For example, view this sample config:
type: S3
bucket: ${bucket_name}
endpoint: ""
region: ${your_bucket_region}
access_key: ${your_access_key}
insecure: false
signature_version2: false
#encrypt_sse: false <-- THIS LINE NEEDS TO BE DELETED
secret_key: ${your_secret_here}
"X-Amz-Acl": "bucket-owner-full-control"
idle_conn_timeout: 90s
response_header_timeout: 2m
insecure_skip_verify: false
enable: true
part_size: 134217728
The easiest way to do this is to delete the existing secret and upload a new one:
kubectl delete secret -n kubecost kubecost-thanos
Update your secret .YAML file as above, and save it as object-store.yaml.
kubectl create secret generic kubecost-thanos -n kubecost --from-file=./object-store.yaml
Once this is done, you're ready to upgrade!
©2023 Stackwatch, Inc. All rights reserved. Designed & built in California.