Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

k8s-credential-provider manifest is missing ate-otel-config envFrom, failing OTLP metric exports to [::1]:4317 / 127.0.0.1:4317 every 60s

Aperta Adatta ai principianti
  • Qualcosa non va?
#3,282 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
82/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
observability

Direzione di ricerca

Leggi manifests/egress-credential-injection/k8s-credential-provider.yaml intorno alle righe 73–118 e confrontalo con il container ext-proc in manifests/ate-install/atenet-egress.yaml intorno alle righe 1419–1427. Controlla il Deployment generato con il comando fornito kubectl get deploy; il lavoro è concluso quando carica ate-otel-config e imposta OTEL_RESOURCE_ATTRIBUTES affinché le metriche del provider usino l’endpoint del collector configurato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area/dev-infra area/observability area/security kind/bug
Summary & Root Cause

Every control-plane container gets its OTLP endpoint from the ate-otel-config ConfigMap through envFrom. The k8s-credential-provider Deployment, deployed when --credential-provider='{"name":"k8s.io"}' is set, omits it. The OpenTelemetry SDK therefore uses its default endpoint localhost:4317, where nothing listens, and every 60s export fails. All provider metrics are lost on GKE, and on Kind the OTEL_METRICS_EXPORTER choice in ate-otel-config is ignored.

Affected Code Locations
  • manifests/egress-credential-injection/k8s-credential-provider.yaml:73-118 (container spec has args, ports, probes and volumeMounts, but no env or envFrom)
  • manifests/ate-install/atenet-egress.yaml:1419-1427 (ext-proc container for comparison: OTEL_RESOURCE_ATTRIBUTES plus envFrom: [{configMapRef: {name: ate-otel-config}}], with a comment explaining that without it the SDK falls back to localhost:4317)
Detailed Reproduction Guide

  1. Deploy with the bundled Kubernetes credential provider:

    go run ./cmd/ate-setup deploy ate-system --credential-provider='{"name":"k8s.io"}'

  2. Inspect the spec and the logs:

    kubectl get deploy -n ate-system k8s-credential-provider -o jsonpath='{.spec.template.spec.containers[0].envFrom}'
kubectl logs -n ate-system -l app=k8s-credential-provider --tail=20
Expected vs. Actual Behavior
  • Expected: Deployment/k8s-credential-provider loads ate-otel-config (and sets OTEL_RESOURCE_ATTRIBUTES) like the other ate-system components, and exports metrics to the cluster collector.
  • Actual: envFrom is empty. The logs show failed to upload metrics: exporter export timeout against 127.0.0.1:4317 / [::1]:4317 every 60s.
Observed Output & Logs
  {"time":"2026-10-27T00:48:43.421326933Z","level":"INFO","msg":"Metrics initialized","otlp_export":true}
  {"time":"2026-10-27T00:49:53.43116369Z","level":"INFO","msg":"failed to upload metrics: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp 127.0.0.1:4317: connect: connection refused\""}
  {"time":"2026-10-27T00:50:53.42768382Z","level":"INFO","msg":"failed to upload metrics: exporter export timeout: rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing: dial tcp [::1]:4317: connect: cannot assign requested address\""}

  01:59:59  failed to upload metrics: ... dial tcp [::1]:4317: connect: cannot assign requested address
  02:00:59  failed to upload metrics: ... dial tcp [::1]:4317: connect: cannot assign requested address
  02:01:59  failed to upload metrics: ... dial tcp [::1]:4317: connect: cannot assign requested address
Lingua principale
Go
Stelle
5.9k
Fork
637
Merge medio
2g 10h
PR unite (30g)
556

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agent-substrate/substrate

Tutte le issue di agent-substrate/substrate

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.