Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 0 additions & 5 deletions .changeset/clickstack-values-key.md

This file was deleted.

5 changes: 0 additions & 5 deletions .changeset/dashboards-include-release-namespace.md

This file was deleted.

7 changes: 7 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,12 @@
# helm-charts

## 3.8.0

### Minor Changes

- d6d89a9: feat: rename the top-level `hyperdx` values key to `clickstack`. Values files that still use `hyperdx` keep working and get a deprecation warning in the install notes; where both keys set the same value, `hyperdx` wins.
- 3dd7921: feat: add `clickstack.dashboards.includeReleaseNamespace` (default `true`, unchanged behaviour). Set it to `false` with `clickstack.dashboards.namespaces: [<ns>]` to confine the dashboard watcher, and its ConfigMap read access, to the listed namespaces: the chart then renders a namespaced Role and RoleBinding in each listed namespace, no ClusterRole, and nothing in the release namespace. Those objects are named `<fullname>-<release namespace>-dashboard-provisioner-scoped`, distinct from the RoleBindings the cross-namespace mode renders, so the flag can be flipped either way on an existing install: no upgrade has to change an existing RoleBinding's `roleRef`. The render fails if it is `false` with no namespaces listed, or with inline `configMaps` while the release namespace is not watched.

## 3.7.0

### Minor Changes
Expand Down
2 changes: 1 addition & 1 deletion charts/clickstack/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ annotations:
- name: Upgrade Guide
url: https://github.com/ClickHouse/ClickStack-helm-charts/blob/main/docs/UPGRADE.md
type: application
version: 3.7.0
version: 3.8.0
appVersion: 2.46.0
dependencies:
- name: opentelemetry-collector
Expand Down
2 changes: 1 addition & 1 deletion charts/clickstack/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# clickstack

![Version: 3.7.0](https://img.shields.io/badge/Version-3.7.0-informational?style=flat)
![Version: 3.8.0](https://img.shields.io/badge/Version-3.8.0-informational?style=flat)
![Build Status](https://github.com/ClickHouse/ClickStack-helm-charts/actions/workflows/helm-test.yaml/badge.svg)
[![Artifact Hub](https://img.shields.io/endpoint?url=https://artifacthub.io/badge/repository/clickstack)](https://artifacthub.io/packages/helm/clickstack/clickstack)

Expand Down
2 changes: 1 addition & 1 deletion docs/UPGRADE.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

Each section lists what changes when you upgrade to that chart version and anything you have to do first, newest first. A version that isn't listed needs nothing beyond `helm upgrade`. The full list of changes is in [CHANGELOG.md](../CHANGELOG.md).

## Unreleased
## 3.8.0

- The top-level `hyperdx` values key is now `clickstack`. Values files and `--set hyperdx.*` flags still work and print a deprecation warning in the install notes; move them under `clickstack` before a future chart version removes `hyperdx`. Where both keys set the same value, `hyperdx` wins. Rendered resources don't change. `--reuse-values` keeps the release's stored `hyperdx` values, which then override anything you move under `clickstack`, so do the upgrade that moves them with `-f <your values file>` instead.

Expand Down
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{
"name": "helm-charts",
"version": "3.7.0",
"version": "3.8.0",
"private": true,
"main": "index.js",
"repository": "git@github.com:hyperdxio/helm-charts.git",
Expand Down
Loading