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
As stated by @noam-codefresh here #557 (comment) the autopilot installation is missing a crucial patch in the kustomization.yaml resulting in a broken installation when using the --app flag for specifying an argocd version without referencing this repository's kustomization.yaml
As a side note: It would be good if the installation didn't reference this repository's /base or /ha kustomize folder in the first place to give more direct control over the version of argocd that is being used, if at all feasible.
The text was updated successfully, but these errors were encountered:
As a side note: It would be good if the installation didn't reference this repository's /base or /ha kustomize folder in the first place to give more direct control over the version of argocd that is being used, if at all feasible.
i am thinking about changing the installation process to just put the patches in the user's git repository, and then the reference will be explicit, and easy to manually upgrade.
and no more "passing" through the argocd-autopilot repository at all. wdyt?
As stated by @noam-codefresh here #557 (comment) the autopilot installation is missing a crucial patch in the kustomization.yaml resulting in a broken installation when using the
--app
flag for specifying an argocd version without referencing this repository's kustomization.yamlAs a side note: It would be good if the installation didn't reference this repository's /base or /ha kustomize folder in the first place to give more direct control over the version of argocd that is being used, if at all feasible.
The text was updated successfully, but these errors were encountered: