openshift-snc: align cluster ingress domain with the nip.io access domain (crc.testing split-brain)

Abierto
#968 0 comentarios 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 4 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
aws, go, kubernetes

Línea de trabajo

Start with pkg/provider/ibmcloud/action/snc/snc.go and trace how the current floating IP, CRC startup, and cluster readiness are handled; inspect the AWS equivalent as well. The issue describes install-time domain setup and post-readiness migration, including console routes and certificates, so first map the existing lifecycle and identify which approach the project can support. Done means cluster-generated domains and routes resolve through nip.io, including after IP rotation; consumers of immutable ingresses.config need install-time configuration or an override.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

mapt ibmcloud openshift-snc create (and the AWS equivalent) runs OpenShift Local with its default domain (apps-crc.testing) but exposes the cluster externally via *.apps.<floating-ip>.nip.io. Names under apps-crc.testing only resolve inside the VM, so every URL the cluster generates — oc get route, operator and app URLs, OAuth redirects — is unreachable from the user's machine.

Verified on a live cluster (openshift-local 4.22)
  • Patching ingresscontroller/default spec.domain works: new hostless routes get the new domain from route admission. status.domain is never re-derived (cosmetic).
  • ingresses.config/cluster spec.domain is immutable after install. Anything reading it — the console operator, the ingress canary controller, e2e deploy scripts using the standard idiom — keeps getting apps-crc.testing, and this cannot be fixed post-install.
  • The console must be served via its custom-route mechanism (console-custom + the default route as redirector); recreating the default route under the new domain collides (HostAlreadyClaimed) and degrades the operator.
  • The router's default certificate must cover the new domain (e.g. via spec.defaultCertificate).
  • Application-operator routes are fine: recreated after the patch, they get the new domain.
Request — two complementary changes

A. Install-time base domain (the complete fix; new clusters only): have the catalog image's self-start service run crc config set base-domain <domain> before the first crc start. Per-instance input already flows via cloud-config (/opt/crc/eip); extend it with the domain — no per-cluster images needed. With nip.io this requires a stable IP (reserved floating IP, or stop-instead-of-destroy between uses). With a real DNS domain (see #273) no stable IP is needed: the baked domain never changes, only the DNS record is updated per boot, and CRC's own certificates stay valid because they are issued for the domain.

B. Post-readiness migration (the only fix for existing clusters): on each provision, with the current floating IP:

  1. patch ingresscontroller.spec.domain to apps.<ip>.nip.io
  2. serve console/downloads via their custom routes
  3. sweep all routes carrying the previous IP or apps-crc.testing hosts
  4. ensure the default ingress certificate covers the new domain

Neither alone is sufficient: A cannot reach snapshot-restored clusters (the domain is baked at first start), B cannot fix ingresses.config readers.

A B
Fixes ingresses.config readers yes no
Works on existing clusters no yes
Needs a stable IP only with nip.io no

Happy to test a PR or preview build; a full runbook from our live-cluster verification is available on request.

Lenguaje dominante
Go
Estrellas
25
Forks
41
Merge medio
5 d 3 h
PR fusionados (30 d)
16

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de redhat-developer/mapt

Todos los issues de redhat-developer/mapt

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.