Open tobiwanobi opened 6 months ago
tobiwanobi
commented
6 months ago Works with the workaroud described in #351 with the following command: argocd-autopilot repo bootstrap --insecure --app "github.com/argoproj-labs/argocd-autopilot/manifests/insecure?ref=v0.4.17"
tobiwanobi
commented
6 months ago Another quick note, with the above workaround (I am not sure if its because of that) the autopilot-bootstrap Application has not been created so I wrote my own Application and deployed it manually to the cluster and now it seems to work properly. Not sure how this one looks when the autopilot creates it, but at least its working. ` apiVersion: argoproj.io/v1alpha1 kind: Application metadata: creationTimestamp: null labels: app.kubernetes.io/managed-by: argocd-autopilot app.kubernetes.io/name: autopilot-bootstrap name: autopilot-bootstrap namespace: argocd spec: destination: namespace: argocd server: https://kubernetes.default.svc ignoreDifferences:
I also created my own kustomization.yaml to pin the v2.9.0 of ArgoCD, this could also be more comfortable for users.
When I try to bootstrap a repo with the --insecure flag I get an error message: FATAL failed to build bootstrap manifests: failed running kustomization: accumulating resources: accumulation err='accumulating resources from 'manifests/insecure': evalsymlink failure on '/usr/local/bin/auto-pilot3429112549/manifests/insecure' : lstat /usr/local/bin/auto-pilot3429112549/manifests: no such file or directory': evalsymlink failure on '/usr/local/bin/auto-pilot3429112549/manifests/insecure' : lstat /usr/local/bin/auto-pilot3429112549/manifests: no such file or directory
But without the insecure flag it works just fine.
I tried this on Ubuntu 22.04 with downloading the latest release v0.4.17 and also an Windows with downloading the latest version with chocolatey v0.2.28 and both did not work with the same error message.