We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checklist:
argocd version
Describe the bug
The ApplicationSet controller isn't bundled with ArgoCD 2.3.0 when installing via kustomize, only in the generated yaml files
To Reproduce
$ curl -sL https://github.com/argoproj/argo-cd/raw/v2.3.0/manifests/ha/install.yaml |grep -m1 ApplicationSet kind: ApplicationSet
$ cat kustomization.yaml apiVersion: kustomize.config.k8s.io/v1beta1 kind: Kustomization resources: - https://github.com/argoproj/argo-cd//manifests/ha/cluster-install?ref=v2.3.0 $ kustomize build . |grep -m1 ApplicationSet $
Expected behavior
Expected that the ApplicationSet controller is installed along with ArgoCD when installing via kustomize remote
Screenshots
Version
$ argocd version argocd: v2.3.0+fe42780 BuildDate: 2022-03-06T06:27:40Z GitCommit: fe427802293b090f43f91f5839393174df6c3b3a GitTreeState: clean GoVersion: go1.17.6 Compiler: gc Platform: linux/amd64 FATA[0000] Argo CD server address unspecified
Logs
Paste any relevant application logs here.
The text was updated successfully, but these errors were encountered:
Duplicate of #8699
Sorry, something went wrong.
No branches or pull requests
Checklist:
argocd version
.Describe the bug
The ApplicationSet controller isn't bundled with ArgoCD 2.3.0 when installing via kustomize, only in the generated yaml files
To Reproduce
$ curl -sL https://github.com/argoproj/argo-cd/raw/v2.3.0/manifests/ha/install.yaml |grep -m1 ApplicationSet kind: ApplicationSet
Expected behavior
Expected that the ApplicationSet controller is installed along with ArgoCD when installing via kustomize remote
Screenshots
Version
Logs
The text was updated successfully, but these errors were encountered: