RBAC not generated for k8s_attributes processor after change to snake-case naming

[jmickey]

Component(s)

collector

What happened?

Description

The k8sattributes processor has been renamed to k8s_attributes as part of snake-case standardisation. See: open-telemetry/opentelemetry-collector-contrib#45901

When using the new name the operator doesn't recognise it and RBAC is not generated.

Steps to Reproduce

1. Create collector config with k8s_attributes processor
2. Deploy collector and witness failed to list *v1.Pod error logs
3. Check ClusterRole, no RBAC rules for k8s_attributes created

Expected Result

RBAC rules are correctly generated when using new snake-case name for processor

Actual Result

RBAC rules are not generated

Kubernetes Version

1.32

Operator version

0.148.0

Collector version

0.148.0

Environment information

No response

Log output

E0402 00:01:49.447467       1 reflector.go:204] "Failed to watch" err="failed to list *v1.Pod: pods is forbidden: User \"system:serviceaccount:opentelemetry:node-collector\" cannot list resource \"pods\" in API group \"\" at the cluster scope" logger="UnhandledError" reflector="k8s.io/client-go@v0.35.2/tools/cache/reflector.go:289" type="*v1.Pod"

E0402 00:30:09.493102       1 reflector.go:204] "Failed to watch" err="failed to list *v1.PartialObjectMetadata: Get \"https://172.20.0.1:443/apis/apps/v1/replicasets?limit=500&resourceVersion=0\": dial tcp 172.20.0.1:443: connect: operation not permitted" logger="UnhandledError" reflector="k8s.io/client-go@v0.35.2/tools/cache/reflector.go:289" type="*v1.PartialObjectMetadata"

Additional context

No response

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[jmickey]

I am willing to work on this, feel free to assign to me