Skip to content

[Backport release-1.5] fix(telemetry): make the documented opt-out cover both collectors - #3917

Draft
github-actions[bot] wants to merge 1 commit into
release-1.5from
backport-3791-to-release-1.5
Draft

github-actions[bot] wants to merge 1 commit into
release-1.5from
backport-3791-to-release-1.5

Conversation

@github-actions

Copy link
Copy Markdown

Description

Backport of #3791 to release-1.5.

@github-actions

Copy link
Copy Markdown
Author

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin backport-3791-to-release-1.5
git worktree add --checkout .worktree/backport-3791-to-release-1.5 backport-3791-to-release-1.5
cd .worktree/backport-3791-to-release-1.5
git reset --hard HEAD^
git cherry-pick -x c3cead8f6455ea9d98804ed6902c260f6c25c744
git push --force-with-lease

Backport of #3791 to release-1.5.

The automated backport stopped on a conflict in
packages/core/installer/values.yaml and committed the markers. Two
differences, not one: the branch pins the operator at v1.5.4, and it has
no platformVersion key at all, which main added later. Resolved by taking
only the new disableTelemetry key and its comment, keeping this branch's
image pin and not importing platformVersion along with it.

Signed-off-by: Andrei Kvapil <[email protected]>
@kvaps
Andrei Kvapil (kvaps) force-pushed the backport-3791-to-release-1.5 branch from 5872d9d to fc98a4b Compare August 20, 2026 12:28
@github-actions github-actions Bot added size/L This PR changes 100-499 lines, ignoring generated files area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/bug Categorizes issue or PR as related to a bug labels Aug 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/release Issues or PRs related to release tooling (changelog, backport, release pipeline) kind/bug Categorizes issue or PR as related to a bug size/L This PR changes 100-499 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant