-
Notifications
You must be signed in to change notification settings - Fork 465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature request - Allow AnnotationsTobeSkipped to be configurable #1525
Comments
/assign |
hi @nidhik ,try modify
this should help |
Hello! I work with @nidhik. Unfortunately that does not seem to solve our problem as it only ignores propagating annotations to the Kubernetes resources. The annotations are still scraped as part of the ClickHouse operator metrics. Although I add
I also tried with Resulting kubernetes resources
Snippet of scraped clickhouse operator metrics
|
@nidhik , fixed in 0.24.1 (not released yet). This is a part of operator configuration now:
|
We use internal tooling to update the ClickHouseInstallation when we would like to kick off a reconcile task. This internal tooling inserts a number of custom build annotations into the resource for internal tracking purposes which includes unique hashes and timestamps.
An unfortunate consequence of this is that a new prometheus series is created by the exporter for each reconcile that the operator initiates since these annotations are read by the exporter from the CHI and added as prometheus labels:
clickhouse-operator/pkg/metrics/metrics.go
Line 124 in 4bf622e
Digging deeper, looks like some annotations can be skipped but this is currently a hardcoded list:
clickhouse-operator/pkg/util/k8s.go
Line 30 in 4bf622e
We would appreciate the ability to configure custom annotations to ignore.
The text was updated successfully, but these errors were encountered: