cluster chart generates invalid YAML when type is not equal to timescaledb

Open Beginner friendly
#1,057 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 3 days

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
78/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
helm, yaml
Domain
build-system

Research direction

Start with charts/cluster/templates/cluster.yaml around line 88 and compare the rendered .spec.postgresql value for non-TimescaleDB clusters with the linked Cluster specification. Render the chart with a type other than timescaledb, then validate the output with kubeconform. Done when .spec.postgresql is an empty object and the rendered YAML validates.

Written by the indexing model from the issue text.

Description

chart( cluster )

I noticed that the cluster chart generates invalid YAML. kubeconform complains that .spec.postgresql is null when type is not set to timescaledb (https://github.com/cloudnative-pg/charts/blob/main/charts/cluster/templates/cluster.yaml#L88) while the specification requires an empty object: https://cloudnative-pg.io/docs/1.30/cloudnative-pg.v1#clusterspec

Dominant language
Go Template
Stars
635
Forks
270
Avg merge
4d 10h
Merged PRs (30d)
20

Getting set up

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 cloudnative-pg/charts

All issues in cloudnative-pg/charts

Similar issues

More Build System issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.