Grafana Dashboards not being installed as expected
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- kubernetes, yaml
- Domain
- infrastructure, observability
Research direction
Start with values.yaml and the chart templates that render the dashboard ConfigMap; inspect the rendered annotations and how grafana_folder is handled. Reproduce the install with dashboards enabled, then verify the ConfigMap applies without the annotation-size error and that dashboards are placed in the requested clickhouse folder.
Written by the indexing model from the issue text.
Description
I am using the latest operator (0.25.5) and when I enable the creation of Grafana dashboards, then I am getting the following error:
The ConfigMap "clickhouse-operator-dashboards" is invalid: metadata.annotations: Too long: may not be more than 262144 bytes
I am using the following values.yaml when applying the operator Helm chart:
nameOverride: clickhouse-operator
serviceMonitor:
enabled: true
additionalLabels:
release: kube-prometheus-stack
team: "platform"
dashboards:
enabled: true
additionalLabels:
grafana_dashboard: "1"
release: kube-prometheus-stack
grafana_folder: "clickhouse"
Currently my workaround is to output the manifests to disk and then I break out the dashboard ConfigMap into its own yaml file so I can apply it using the --server-side flag:
kubectl apply --server-side -f dashboards.yaml
However, I noticed that even then the dashboards were not put into the specified "clickhouse" folder.
It seems that the setting grafana_folder: "clickhouse" doesn't do anything. I pulled the chart locally and did a search across the entire chart for grafana_folder and indeed this value is not being used in any of the templates of the chart at the moment.
Hope that helps! Let me know if there is any more information I can provide. Thank you for creating this operator and making it OSS!
- Dominant language
- Go
- Stars
- 2.6k
- Forks
- 577
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Altinity/clickhouse-operator
-
Counter metrics are missing the conventional _total suffixPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Altinity/clickhouse-operator#2093 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Altinity/clickhouse-operator#2098 ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Altinity/clickhouse-operator#2096 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
Altinity/clickhouse-operator#2094 ·
Maintainers usually reply within 2 days
-
[Regression / Discussion] Loss of hot-reloaded password rotation after removal of k8s_secret_* in 0.27.4Possibly taken @sunsingerus claimed this 4 days ago. Openplanned for review
Difficulty 5/5 Over a week Newbie friendliness 38/100
Altinity/clickhouse-operator#2092 · 2 comments · 1 assignee ·
Maintainers usually reply within 2 days
All issues in Altinity/clickhouse-operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
duplication
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
openvibely/openvibely#1443 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
keyxmakerx/Chronicle#1179 ·
Maintainers usually reply within 1 day
-
raised-by:worker
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
medici-finance/assay#2486 ·
Maintainers usually reply within 1 day
-
area/testing kind/bug triage/needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cozystack/cozystack#4841 · 1 reaction ·
Maintainers usually reply within 2 days