feature: monitoring-logging 1.0.16 - #407
Draft
infojohn wants to merge 2 commits into
Draft
Conversation
Release-branch placeholder for monitoring-logging 1.0.16 (next patch on the 1.0.x line; previous release monitoring-logging-1.0.15 was cut from PR #395). - chore(monitoring-logging): bump chart version to 1.0.16 (Chart.yaml version + appVersion, README badges) - added upgrade file — docs/upgrade-from-1.0.15-to-1.0.16.md (no functional changes yet; placeholder for patches landing on this branch) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Mirrors charts/podiumd/.helmignore, which exists because podiumd already hit the Kubernetes 1 MiB release-Secret limit once (everything in the packaged chart is embedded in that Secret). monitoring-logging had no .helmignore at all, so its docs/, scripts/, and leftover .github/ (from when this chart lived in its own repo) were shipping in every release Secret for no functional reason — dashboards/ is deliberately kept, since templates load it via .Files.Get. Drops the estimated release-Secret payload from 407,160 to 341,480 bytes (38.8% -> 32.6% of the 1 MiB limit; measured with the estimator from #408). helm lint and helm template are unaffected (same 53,576 lines of rendered output). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
15 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release-branch placeholder for monitoring-logging 1.0.16 (next patch on
the 1.0.x line; previous release
monitoring-logging-1.0.15was cutfrom PR #395).
Contents
chore(monitoring-logging): bump chart version to 1.0.16— Chart.yamlversion+appVersion, plus README Version/AppVersion badges.docs/upgrade-from-1.0.15-to-1.0.16.md(no functional changes yet; placeholder for patches landing on this
branch)
chore(monitoring-logging): add .helmignore— mirrorscharts/podiumd/.helmignore(podiumd already hit the Kubernetes1 MiB release-Secret limit once). Excludes
docs/,scripts/, andleftover
.github/from the packaged chart;dashboards/is keptsince templates load it via
.Files.Get. Drops the estimatedrelease-Secret payload from 407,160 to 341,480 bytes (38.8% -> 32.6%
of the 1 MiB limit — see the estimator added in feat: release-secret size estimator + /helm-render-all check #408).
Policy
Test plan
Verification results
1 chart(s) linted, 0 chart(s) failed. Only note isthe pre-existing
[INFO] Chart.yaml: icon is recommended.skipping globalsinfo line. 53,576 lines of output, unchangedbefore/after the
.helmignoreaddition (it only affects packaging,not rendering).
helm.sh/chart: monitoring-logging-1.0.16on labelled resources.
🤖 Generated with Claude Code