fix(operational-review): correct kyverno container label and memory limit#11
Open
drewr wants to merge 1 commit into
Open
fix(operational-review): correct kyverno container label and memory limit#11drewr wants to merge 1 commit into
drewr wants to merge 1 commit into
Conversation
…imit - Replace container="kyverno-admission-controller" with container="kyverno" in all three metric queries (memory usage, memory limit, restart rate); the former label returns no data in VictoriaMetrics — cAdvisor and kube-state-metrics use the container name "kyverno", not the pod name. - Add namespace="kyverno-system" scoping to each corrected query. - Update stale 1536Mi memory limit comment to 2048Mi (2Gi), confirmed across all 18 clusters from live prod metrics. - Flag kyverno_update_requests_total as unavailable in the current Kyverno deployment; direct operators to the Kubernetes MCP UpdateRequest path. Co-Authored-By: Claude Sonnet 4.6 <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
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.
Summary
Three fixes to
skills/operational-review/queries.md, all diagnosed from live VictoriaMetrics prod data:Container label mismatch (3 queries): Queries filtering
container="kyverno-admission-controller"returned no data. The actual label value used by cAdvisor and kube-state-metrics iscontainer="kyverno"(confirmed vialabel_values). All three affected queries (memory working set, memory limit, restart rate) are corrected tocontainer="kyverno"and scoped withnamespace="kyverno-system".Stale memory limit comment: The comment referencing the post-infra#2220 memory limit said
1536Mi. The actual current limit confirmed across all 18 clusters is 2048Mi (2Gi). Updated accordingly.kyverno_update_requests_totalunavailable: This metric is not emitted by the Kyverno version running in prod (absent from VictoriaMetrics). A NOTE block is added to that query section directing operators to use the Kubernetes MCPUpdateRequestpath (already documented above it) as the only viable approach.Also bumps
datum-platformplugin version1.6.0 → 1.6.1per release checklist.Test plan
container_memory_working_set_bytes{namespace="kyverno-system", container="kyverno"}returns data in prod VictoriaMetricskube_pod_container_resource_limits{namespace="kyverno-system", resource="memory", container="kyverno"}returns data and limit value matches 2048Miincrease(kube_pod_container_status_restarts_total{namespace="kyverno-system", container="kyverno"}[1d])returns datakyverno_update_requests_totalremains absent from VictoriaMetrics (NOTE block is accurate)Generated with Claude Code