kubectl proxy doesn't serve the webUI

Aperta
#5,722 3 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

Nessuno ha ancora preso questa issue.

  • #5724 di @lbarrosby — chiusa senza merge

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
22/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
networking

Direzione di ricerca

The failure is a stream error ... INTERNAL_ERROR from kubectl proxy (proxy_server.go), not from Alertmanager itself, so the cause probably lies in how the Kubernetes apiserver proxy handles the service-proxy path. Reproduce by hitting the services/alertmanager-operated:9093/proxy URL through kubectl proxy at v0.32.0 and compare against v0.31.1. Done means the proxied UI loads again and the reproduction is confirmed against both client versions.

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

Descrizione

component/ui
What did you do?

When trying to use the kubectl proxy command after upgrading from v0.31.1 to v0.32.0 I tried to reach the alertmanager UI using the URLs:

  • http://127.0.0.1:8001/api/v1/namespaces/monitoring/services/alertmanager-operated:9093/proxy
  • http://127.0.0.1:8001/api/v1/namespaces/monitoring/services/alertmanager-operated:9093/proxy/#/alerts

None of these works after the upgrade, which they did before the upgrade.
The API is still working as expected from what I can see.

Tested on kubernetes v1.35.6 and kubectl v1.35.10

Using kubectl port-forward works as expected, only kubectl proxy seems to be broken

What did you expect to see?

Be redirected to /#/alerts and see the web UI

What did you see instead? Under which circumstances?

The browser shows

stream error: stream ID 1; INTERNAL_ERROR; received from peer

And the output from kubectl proxy is

E1103 15:32:34.220447 1186201 proxy_server.go:147] Error while proxying request: stream error: stream ID 1; INTERNAL_ERROR; received from peer
System information

No response

Alertmanager version
Broken versions:
version=0.32.0, branch=HEAD, revision=685a2a1c6bb01b2c17bc1bfae995cb3416c1115e
version=0.34.2, branch=HEAD, revision=e8349048265ccc0871c3d0d668b05eacc68baf50

Working version:
version=0.31.1, branch=HEAD, revision=7a639ba087d6e877038cabfdaa645230f79001b8
Alertmanager configuration file

Prometheus version

Prometheus configuration file

Logs

CPU profiles

No response

Memory profiles

No response

Number of alerts

No response

Number of silences

No response

prometheus-operator checklist
  • I have confirmed this issue is not caused by a missing feature in prometheus-operator.
  • I have reproduced this issue when running Alertmanager directly (without prometheus-operator).
Lingua principale
Go
Stelle
8.7k
Fork
2.5k
Merge medio
5g 21h
PR unite (30g)
43

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Ha un modello di pull request
  • Nessuna guida per i contributori

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 prometheus/alertmanager

Tutte le issue di prometheus/alertmanager

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.