search

jaegertracing / helm-charts

Helm Charts for Jaeger backend
Apache License 2.0
269 stars 348 forks source link

[Bug]: Cannot call Webhook mjeager.kb.io In Default Deployment #400

Open TitanRob16 opened 2 years ago

TitanRob16 commented 2 years ago

What happened?

The documentation doesn't appear to be descriptive enough in the setup of Jaeger. I've followed both the Github and jaegertracing.io docs in their simplest form, and I'm immediately running into issues deploying a new Jaeger instance, as described below.

Steps to reproduce

  1. Follow the steps here to install Jaeger via Helm: https://github.com/jaegertracing/helm-charts/tree/main/charts/jaeger-operator
  2. Try to create a new Jaeger instance using: apiVersion: jaegertracing.io/v1 kind: Jaeger metadata: name: simplest
  3. Error: Internal error occurred: failed calling webhook "mjaeger.kb.io": Post "https://jaeger-operator-webhook-service.observability.svc:443/mutate-jaegertracing-io-v1-jaeger?timeout=10s": context deadline exceeded

Expected behavior

I expect a new Jaeger instance to be deployed.

Relevant log output

No response

Screenshot

No response

Additional context

No response

Jaeger backend version

1.37.0

SDK

No response

Pipeline

No response

Stogage backend

No response

Operating system

Linux, GKE

Deployment model

Kubernetes

Deployment configs

No response

ra-ramos commented 2 years ago

I had the same issue here... I managed to fix it by deleting the mutatingwebhookconfigurations (jaeger-operator-mutating-webhook-configuration) and the ValidatingWebhookConfiguration (jaeger-operator-validating-webhook-configuration).