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
Hi,
When creating an Instrumentation resource on a AWS EKS cluster I encounter the following error:
Error from server (InternalError): error when creating "m.yaml": Internal error occurred: failed calling webhook "mopentelemetrycollector.kb.io": Post: https://opentelemetry-operator-webhook.NAMESAPCE.svc/mutate-opentelemetry-io-v1alpha1-opentelemetrycollector?timeout=10s Address is not allowed
@TylerHelmuth Hm... Address is not allowed is quite a generic error message. I tried to dig out if from Golang standard library but didn't find exact matches.
@ilyamochalov I know this issue has been around for a few months. But I encountered the same problem recently when installed OTEL on a cluster with the Calico CNI Installed. Are you using the base EKS VPC CNI or you using a different CNI like Calico?
Component(s)
instrumentation
Describe the issue you're reporting
Hi,
When creating an Instrumentation resource on a AWS EKS cluster I encounter the following error:
AWS EKS: v1.26.7-eks-2d98532
Open-telemetry operator: 0.39.2
This issue is similar to:
Steps to reproduce
Install the operator in an existing private EKS cluster where
Once the opentelemetry-operator deployment is ready, create an OpenTelemetry Instrumentation resource:
Solution
Use
hostNetwork: true
https://github.com/open-telemetry/opentelemetry-helm-charts/blob/opentelemetry-operator-0.41.0/charts/opentelemetry-operator/values.yaml#L251Where is a good place to document this configuration consideration?
The text was updated successfully, but these errors were encountered: