Manager does not detect Route CRD that appears after startup
I maintainer di solito rispondono entro 1 giorno
@atishay-kasliwal ci sta già lavorando.
Dal 19/11/2026.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 48/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Go
- Stelle
- 190
- Fork
- 367
- Merge medio
- 4g 2h
- PR unite (30g)
- 63
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di redhat-developer/gitops-operator
-
NamespaceManagement revocation checks labels on the wrong namespaceForse già presa @Rizwana777 l’ha presa 3 giorni fa. Apertakind/bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
redhat-developer/gitops-operator#1559 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Deleting an ArgoCD instance removes RBAC belonging to same-named instancesForse già presa @Rizwana777 l’ha presa 3 giorni fa. Apertakind/bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 45/100
redhat-developer/gitops-operator#1558 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
NamespaceManagement cleanup can delete RBAC in unrelated namespacesForse già presa @Rizwana777 l’ha presa 3 giorni fa. Apertakind/bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 22/100
redhat-developer/gitops-operator#1557 · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
ApplicationSet tokenRef strict mode changes only apply after the controller is restartedForse già presa @Gabrielandre02 l’ha presa 5 giorni fa. Aperta
redhat-developer/gitops-operator#1554 · 1 commento · 1 assegnatario ·
I maintainer di solito rispondono entro 1 giorno
-
Enqueue the previous Argo CD instance when NamespaceManagement consent is withdrawnForse già presa @Gabrielandre02 l’ha presa 5 giorni fa. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 25/100
redhat-developer/gitops-operator#1530 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di redhat-developer/gitops-operator
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Inconsistency between golang and cue in specForse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
I maintainer di solito rispondono entro 1 giorno
-
security
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
Tencent/LoopForge#1087 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno