Accept PodTemplate annotations

Open
#365 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go, kubernetes

Research direction

Start from the ClickHouse CRD's PodTemplateSpec definition in the Go API types, and trace how the root-level annotations are currently copied onto pods and services. The issue asks for annotations to be accepted under the pod template, so the schema and the reconcile logic that applies them both need changing. Done means a pod template annotation reaches the pods without being added to the services, and the existing tests still pass.

Written by the indexing model from the issue text.

Description

feature
Company or project name

No response

Use case

The annotations setup at root level of the CRD are passed to both pods and services, this leads to duplicated metrics scraping when prometheus has jobs to scrape both job="kubernetes-pods" and job="kubernetes-service-endpoints".

Describe the solution you'd like

In CRDs it would be nice to be able to also pass annotations in the PodTemplateSpec which is currently not allowed.

Describe alternatives you've considered

No response

Additional context

No response

Dominant language
Go
Stars
310
Forks
46
Avg merge
1d 15h
Merged PRs (30d)
21

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ClickHouse/clickhouse-operator

All issues in ClickHouse/clickhouse-operator

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.