Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Webhook "address is not allowed" when creating an Instrumentation on EKS #2260

Open
ilyamochalov opened this issue Oct 24, 2023 · 5 comments
Labels
area:auto-instrumentation Issues for auto-instrumentation needs triage

Comments

@ilyamochalov
Copy link

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:

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

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#L251

Where is a good place to document this configuration consideration?

@TylerHelmuth TylerHelmuth added the area:auto-instrumentation Issues for auto-instrumentation label Oct 24, 2023
@TylerHelmuth
Copy link
Member

I'd like to understand more about this issue and why using hostNetwork is a solution. I do not believe this is pervasive to all AWS EKS clusters.

@TylerHelmuth
Copy link
Member

@ilyamochalov what are you using to manage the certificates?

@ilyamochalov
Copy link
Author

@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.

For certificates we are using https://github.com/cert-manager/cert-manager/tree/v1.10.1/deploy/charts/cert-manager

@AlecAttwood
Copy link

@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?

@ilyamochalov
Copy link
Author

@AlecAttwood I am using Calico too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:auto-instrumentation Issues for auto-instrumentation needs triage
Projects
None yet
Development

No branches or pull requests

3 participants