Repository navigation
metrics: Monitor policies in their workloads' manifests - #9
Merged
Merged
Conversation
Radarr's and Sonarr's monitor policies go into the workload's own instance (the monitor's default, its namespace) instead of manifests of their own: workloads can hold nested instances now, so the policies land with their namespace instead of a k3s pass later. The manifests check turns Alloy on, so the metrics parts of the modules are evaluated; with it off they never were. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
The monitors'
podPortpolicies go into the workload's own instance (the monitor'smanifestdefault, its namespace), not into a<name>-metrics-policymanifest of their own. nixos-homelab/shared#14 lets workload and deployment instances hold nested instances, so a policy now lands with its namespace instead of a k3s pass later. homelab-shared is bumped to it.The manifests check now turns Alloy on, so the modules'
metrics.nixget evaluated. Before, nothing in CI evaluated them.Checked: manifests and deadnix. In example's NAS payload, built from the current mains with these branches, the same 412 objects come out with equal content and labels, and only the policy objects move into their target's manifest. The k3s pruner leaves moved objects alone, because it skips anything a remaining manifest declares.
🤖 Generated with Claude Code