Skip to content
New issue

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

Support ApplicationSets #174

Open
dustinvanbuskirk opened this issue Sep 15, 2021 · 1 comment
Open

Support ApplicationSets #174

dustinvanbuskirk opened this issue Sep 15, 2021 · 1 comment

Comments

@dustinvanbuskirk
Copy link

I have a use case to deploy the same application across multiple destination clusters.

I've found ApplicationSets is ready to support this but Autopilot only has the capability to sync Apps.

Ideally I would like to see an applicationsets folder and be able to place applicationset resource files in that directory and have them automatically deployed.

Also, might be helpful to have the cli support create applicationset

@myspotontheweb
Copy link

myspotontheweb commented Jan 5, 2022

Autopilot already uses ApplicationSets, when it generates a new project. For example, running the following:

argocd-autopilot project create test1

Generates a file, in the projects subdirectory, that contains both a Project and ApplicationSet definition.

Notice how there are place holders for the destination cluster, these values come from the JSON file that is created by running the "app create" command (where you can select the target cluster to deploy against).

 argocd-autopilot app create --help

Laboring the point it is the presence of these configuration files that triggers the ApplicationSet to generate an Application object.

PS

The following is a setup script I used to build my workloads repo. 3 applications deployed to "dev", "test" and "prod".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants