Skip to content

fix(victoria-metrics-agent): add nodes/proxy RBAC permission - #291

Open
davidelkind1 wants to merge 1 commit into
zesty-co:mainfrom
davidelkind1:fix/KPS-6424-victoria-metrics-rbac
Open

fix(victoria-metrics-agent): add nodes/proxy RBAC permission#291
davidelkind1 wants to merge 1 commit into
zesty-co:mainfrom
davidelkind1:fix/KPS-6424-victoria-metrics-rbac

Conversation

@davidelkind1

Copy link
Copy Markdown

Description

Fixes KPS-6424

Victoria Metrics Agent is failing to scrape kubelet resource metrics in all clusters due to insufficient RBAC permissions. The agent receives a 403 Forbidden response when attempting to access .

Root Cause

The ClusterRole for the victoria-metrics-agent service account has permissions for nodes and nodes/metrics, but is missing nodes/proxy.

Solution

This PR adds the missing nodes/proxy permission to the ClusterRole via the rbac.extraRules configuration in the victoriaMetricsAgent section.

Testing

After this change is deployed:

  • Victoria Metrics Agent should successfully scrape kubelet resource metrics
  • No 403 Forbidden errors should appear in the agent logs
  • The kubelet-resource scrape target should report healthy

Related Issue

https://zestyco.atlassian.net/browse/KPS-6424

Fixes KPS-6424

Victoria Metrics Agent needs permission to access nodes/proxy endpoint
to scrape kubelet resource metrics (/metrics/resource). Without this
permission, the agent receives 403 Forbidden errors.

This adds the missing nodes/proxy permission to the ClusterRole via
rbac.extraRules configuration.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant