Feature Request: Component-level Object Store Configuration & Top-level Overrides

[HasaValm]

1. Top-level namespace and fullnameOverride

namespace: ""
fullnameOverride: "" (# change value from .metadata.name)

This would simplify deploying the same chart across multiple environments and make resource naming more predictable.

2. Component-level objstore configuration

Currently, the chart provides a single global object store configuration:

global:
objstore:
createSecret: true
secretName: thanos-objstore

This works well when every component uses the same object store.

However, it becomes limiting for more advanced deployments where different Thanos components need different object store configurations.

One example is a multi-cluster setup, where:

• one cluster runs Compactor against bucket A,
• another cluster runs a Store Gateway serving bucket B,
• both deployments reuse the same chart.

Since the chart only supports a single global objstore Secret, every component is forced to use the same bucket configuration.

It would be great if components that consume an object store could optionally override the global configuration, for example:

global:
objstore:
createSecret: true
secretName: thanos-objstore

storegateway:
objstore:
createSecret: false
secretName: thanos-objstore-dev

If no component-specific configuration is provided, it could simply fall back to global.objstore, so this would be fully backward compatible.

I think this would make the chart much more flexible for multi-cluster, migration, and hybrid deployments without affecting existing users.

[HasaValm]

Hi @hamdikh,

just wanted to follow up on this.

Are there any plans to support component-level objstore configuration as described in point 2 in the future?

Thanks!