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

[occm] Per-Service override for enable-ingress-hostname

Aperta
  • Qualcosa non va?
#3,232 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à
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
40/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go, kubernetes
Ambito
backend, cloud

Direzione di ricerca

No files or tests are named. Start at the LoadBalancer cloud configuration and Service annotation handling, then trace how status.loadBalancer.ingress is populated for PROXY protocol load balancers. Done means the annotation overrides the config option per Service, defaults to the config value, and false produces an IP with ipMode: Proxy; note that the issue says a PR is already ready.

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

Descrizione

kind/feature

/kind feature

What happened:

With enable-ingress-hostname=true in the cloud config, OCCM publishes every PROXY protocol load balancer in the Service status as an <ip>.nip.io hostname (perhaps specific to our Cloud Provider). Anything that reads that status to publish DNS, such as ExternalDNS via the Gateway API, can then only create a CNAME to a nip.io name.

What you expected to happen:

A way for one Service to get the IP with ipMode: Proxy instead, which OCCM already does when the option is off. On a managed cluster the cloud config belongs to the provider, so a tenant cannot turn the option off, and the provider is understandably reluctant to change a default for every customer.

How to reproduce it:

  1. Set enable-ingress-hostname=true under [LoadBalancer] in the cloud config.
  2. Create a type: LoadBalancer Service with loadbalancer.openstack.org/proxy-protocol: "true".
  3. status.loadBalancer.ingress shows hostname: <ip>.nip.io and no ip. No annotation on the Service changes that; loadbalancer.openstack.org/hostname only substitutes another hostname.

Anything else we need to know?:

Proposal: a Service annotation loadbalancer.openstack.org/enable-ingress-hostname that overrides the config option, defaulting to it, in the same way enable-health-monitor overrides create-monitor. Setting it to false yields the IP with ipMode: Proxy, so kube-proxy still leaves the LB IP alone on Kubernetes 1.32 and later. I have a PR ready.

Environment:

  • openstack-cloud-controller-manager(or other related binary) version: v1.33.0
  • OpenStack version: Octavia on Elastx (managed Kubernetes)
  • Others: Kubernetes v1.34.4, Istio Gateway API, ExternalDNS v0.21.0
Lingua principale
Go
Stelle
720
Fork
687
Merge medio
1g 16h
PR unite (30g)
51

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 kubernetes/cloud-provider-openstack

Tutte le issue di kubernetes/cloud-provider-openstack

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.