search

solo-io / gloo-portal-issues

Public tracker for issues related to Gloo Portal
https://docs.solo.io/gloo-portal/latest/
1 stars 3 forks source link

Portal CRDs fail to sync in ArgoCD deployment #116

Closed jameshbarton closed 2 years ago

jameshbarton commented 2 years ago

Describe the bug When deploying Portal 1.1 in an ArgoCD app-of-apps pattern, the Portal CRDs (e.g., apidocs, apiproducts) consistently fail to sync, leaving the Portal ArgoCD app in an out-of-sync state.

To Reproduce

  1. Follow setup directions for ArgoCD, Gloo Edge, and Gloo Portal, using the readme in Solo gitops-library. Observe that gloo-portal-helm app is OutOfSync, as shown in snapshots below. Drill down and observe that specifically it’s failing to add an empty properties object inside openAPIV3Schema stanza on all the Portal CRDs, and Argo just continues retrying. See snaps below.
Screen Shot 2021-09-28 at 7 09 02 AM Screen Shot 2021-09-28 at 7 14 13 AM Screen Shot 2021-09-27 at 5 42 10 PM

Expected behavior The gloo-portal-helm app syncs successfully.

Additional context The GKE cluster is gke_solo-test-236622_us-east1-d_jimb-portal-cbp.

marcogschmidt commented 2 years ago

The fix for this issue has been release in v1.2.0-beta1.