You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have cloned this repo and bootstrapped flux using the getting started guide:
2024-01-16T08:08:35.453Z info Kustomization/apps.flux-system - Dependencies do not meet ready condition, retrying in 30s
2024-01-16T08:08:35.459Z info Kustomization/infra-configs.flux-system - Dependencies do not meet ready condition, retrying in 30s
Issue is brought about by existence of clusters/production/infrastructure.yaml. If i remove it seems to work just fine.
The text was updated successfully, but these errors were encountered:
For those on the fence between Flux and Argo, Flux is often presented as the easier option. For beginners, it would really help if the quick start documentation and repo was robust, detailed, and most of all tested to make sure it all still works. Even as a beginner to k8s and Helm, Flux is simple enough that it's a really good place to get started. Speaking from experience! It's great there is a lot of development and serveral advancements in the application itself, but for the success of the project maintaining a low barrier of entry should not be forgotten as a priority. Thank you for all your hard work!
Have cloned this repo and bootstrapped flux using the getting started guide:
2024-01-16T08:08:35.453Z info Kustomization/apps.flux-system - Dependencies do not meet ready condition, retrying in 30s
2024-01-16T08:08:35.459Z info Kustomization/infra-configs.flux-system - Dependencies do not meet ready condition, retrying in 30s
Issue is brought about by existence of clusters/production/infrastructure.yaml. If i remove it seems to work just fine.
The text was updated successfully, but these errors were encountered: