Manager does not detect Route CRD that appears after startup
Los mantenedores suelen responder en 1 día
@atishay-kasliwal ya está trabajando en esto.
Desde el 19/11/2026.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
Start with cmd/main.go and trace how util.IsRouteAPIFound() controls routev1.AddToScheme; then read the startup call to InspectCluster. The report says both checks happen only once, so investigate where API discovery or CRD events could update the scheme after startup. Done means a Route CRD created after manager startup can be reconciled without restarting the manager.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Describe the bug
On a GKE management cluster where HyperShift is installed through GitOps, the OpenShift GitOps manager starts before the routes.route.openshift.io CRD exists. The manager registers the Route type only at startup: cmd/main.go calls routev1.AddToScheme only when util.IsRouteAPIFound() is true, and InspectCluster runs once. A Route API that appears later is never added to the scheme, so every Route reconciliation fails with:
no kind is registered for the type v1.Route in scheme "pkg/runtime/scheme.go:111"
The ArgoCD instance stays phase=Failed with Reconciled=False until the manager pod is restarted with the Route API present. This is not an edge case for this deployment shape: because the cluster installs HyperShift through Argo CD, the manager always starts before HyperShift creates the Route CRD.
To Reproduce
- Create a GKE cluster and install the OpenShift GitOps 1.22.2 operator, so the manager starts while
route.openshift.iois absent. - Confirm the API group is absent:
kubectl --context "$CTX" api-resources --api-group=route.openshift.io
Expected: no resources listed.
- Install HyperShift through Argo CD. The sync creates
routes.route.openshift.ioroughly 47 minutes after the manager started. - Wait for the operator to reconcile the
ArgoCDinstance.
Actual results
ArgoCD reports phase: Failed, Reconciled: False with the scheme error above. The operator log repeats the same error on each Route reconcile and it persists indefinitely.
Expected behavior
The manager should handle a Route CRD that appears after startup. Two approaches that would satisfy the use case:
- re-run API discovery periodically or on CRD watch events and add the Route type to the scheme once
routes.route.openshift.iois available, or - watch for the CRD itself instead of doing a one-time check at startup.
No claim is made about which approach upstream prefers.
Environment
- OpenShift GitOps 1.22.2, release 7 (
openshift-gitops-operator.v1.22.2) - Advisory RHBA-2026:83602 (2026-10-15)
- Bundle
registry.redhat.io/openshift-gitops-1/gitops-operator-bundle@sha256:2ba58c50f771c08bbc5a1d8572c7b058df55bc71667cc66026d42840eb4bee6d - Operator source
redhat-developer/gitops-operatoratcf32771491be2ed7f03d43d279171d6c265f2d2b - Downstream source
rh-gitops-midstream/releaseat219dafaaf0e9431f8b468b4932f337f3ce397058 - GKE
1.36.4-gke.2377000on Autopilot,REGULARchannel - Config Sync 1.23.3, Argo CD installed by Config Sync from a public bootstrap repo
Additional context
Timeline observed on 2026-11-13 (UTC):
- 16:00:03: manager pod started in
gitops-operator. - 16:46:57: HyperShift CRDs landed on the management cluster API server after the root ApplicationSet synced the management-cluster applications.
- 16:47:00:
routes.route.openshift.iocreated. - 16:47:11 to 17:08:
ArgoCDreportedphase=Failed,Reconciled=False; the scheme error repeated on every Route reconcile. - 17:08: manager pod deleted manually. The replacement registered the Route scheme and the instance reached
phase=Available,Reconciled=True. No Route object was created because every route switch in the instance spec is disabled.
Source reference at the released commit cf327714:
cmd/main.gocallsroutev1.AddToSchemeonly whenutil.IsRouteAPIFound()returns true.InspectClusterruns once at startup.
GITOPS-11466 (PR #1321, release backport #1354, commit 139db716ae65182624429cc1d78cd5a1c625f15c) makes Route detection independent of the Config API. That fixes a manager that starts after the Route CRD exists but with the Config API absent. It does not cover a Route API that appears after startup.
Workaround, either variant restores the manager without a code change:
- Install the Route CRD before the GitOps manager starts.
- Restart the manager once
routes.route.openshift.ioexists:
kubectl --context "$CTX" get crd routes.route.openshift.io
kubectl --context "$CTX" -n "$OPERATOR_NS" rollout restart deployment/openshift-gitops-operator-controller-manager
kubectl --context "$CTX" -n "$OPERATOR_NS" rollout status deployment/openshift-gitops-operator-controller-manager
This was found during a bounded development validation on a disposable GKE cluster. It is not a support or certification statement about this configuration.
- Lenguaje dominante
- Go
- Estrellas
- 190
- Forks
- 367
- Merge medio
- 4 d 2 h
- PR fusionados (30 d)
- 63
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de redhat-developer/gitops-operator
-
NamespaceManagement revocation checks labels on the wrong namespacePosiblemente ocupada @Rizwana777 la tomó hace 3 días. Abiertokind/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
redhat-developer/gitops-operator#1559 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Deleting an ArgoCD instance removes RBAC belonging to same-named instancesPosiblemente ocupada @Rizwana777 la tomó hace 3 días. Abiertokind/bug
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
redhat-developer/gitops-operator#1558 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
NamespaceManagement cleanup can delete RBAC in unrelated namespacesPosiblemente ocupada @Rizwana777 la tomó hace 3 días. Abiertokind/bug
Dificultad 4/5 3-5 días Aptitud para principiantes 22/100
redhat-developer/gitops-operator#1557 · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
ApplicationSet tokenRef strict mode changes only apply after the controller is restartedPosiblemente ocupada @Gabrielandre02 la tomó hace 5 días. Abierto
redhat-developer/gitops-operator#1554 · 1 comentario · 1 asignado ·
Los mantenedores suelen responder en 1 día
-
Enqueue the previous Argo CD instance when NamespaceManagement consent is withdrawnPosiblemente ocupada @Gabrielandre02 la tomó hace 5 días. Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
redhat-developer/gitops-operator#1530 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de redhat-developer/gitops-operator
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
Inconsistency between golang and cue in specPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
Los mantenedores suelen responder en 1 día
-
security
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 73/100
Tencent/LoopForge#1087 · 1 comentario ·
Los mantenedores suelen responder en 1 día