You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
serviceaccount/metrics-custom-sa created
clusterrole.rbac.authorization.k8s.io/otel-role created
clusterrolebinding.rbac.authorization.k8s.io/otel-metrics-rolebinding created
clusterrole.rbac.authorization.k8s.io/target-allocator-cluster-role created
clusterrolebinding.rbac.authorization.k8s.io/target-allocator-clusterrolebinding created
Warning: missing the following rules for monitoring.coreos.com/servicemonitors: [*]
Warning: missing the following rules for services: [get,list,watch]
Warning: missing the following rules for configmaps: [get]
Warning: missing the following rules for discovery.k8s.io/endpointslices: [get,list,watch]
Warning: missing the following rules for networking.k8s.io/ingresses: [get,list,watch]
Warning: missing the following rules for monitoring.coreos.com/podmonitors: [*]
Warning: missing the following rules for nodes: [get,list,watch]
Warning: missing the following rules for nodes/metrics: [get,list,watch]
Warning: missing the following rules for endpoints: [get,list,watch]
Warning: missing the following rules for pods: [get,list,watch]
Warning: missing the following rules for namespaces: [get,list,watch]
Warning: missing the following rules for nonResourceURL: /metrics: [get]
opentelemetrycollector.opentelemetry.io/metrics created
Also any other edits to the metrics OpenTelemetryCollector results in the same warnings.
Kubernetes Version
1.30.0
Operator version
v0.108.0
Collector version
v0.108.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") on WSL, running in minikube (using docker driver).
Log output
No response
Additional context
$ kubectl get pods -o custom-columns=NAME:.metadata.name,SA:.spec.serviceAccountName
NAME SA
metrics-collector-0 metrics-custom-sa
metrics-targetallocator-7d9758598f-v99c6 metrics-targetallocator
my-opentelemetry-operator-cd87d8bdc-r5t64 opentelemetry-operator
When I tried this scenario on my end and changed this warning message to include the user, it turned out the operator checks the system:serviceaccount:default:<EMPTY SA NAME> serviceaccount instead of the generated serviceaccount name.
Warning: missing the following rules for networking.k8s.io/ingresses: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for nodes: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for nodes/metrics: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for endpoints: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for pods: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for discovery.k8s.io/endpointslices: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for nonResourceURL: /metrics: [get,system:serviceaccount:default:]
Warning: missing the following rules for monitoring.coreos.com/servicemonitors: [*,system:serviceaccount:default:]
Warning: missing the following rules for monitoring.coreos.com/podmonitors: [*,system:serviceaccount:default:]
Warning: missing the following rules for services: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for namespaces: [get,system:serviceaccount:default:,list,system:serviceaccount:default:,watch,system:serviceaccount:default:]
Warning: missing the following rules for configmaps: [get,system:serviceaccount:default:]
I can take care of this and try to implement a fix.
Component(s)
No response
What happened?
Description
Might be related to #2685. Not totally convinced that it's not just something I'm doing wrong though.
Steps to Reproduce
Expected Result
No warnings/errors.
Actual Result
Also any other edits to the
metrics
OpenTelemetryCollector results in the same warnings.Kubernetes Version
1.30.0
Operator version
v0.108.0
Collector version
v0.108.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04") on WSL, running in minikube (using
docker
driver).Log output
No response
Additional context
Permissions of Collector service account:
Permissions of Target Allocator service account:
Permissions of the operator itself:
The text was updated successfully, but these errors were encountered: