2019-05-08 16:37:45 +00:00
|
|
|
# Tools
|
2018-07-27 23:51:44 +00:00
|
|
|
|
2019-06-18 17:03:19 +00:00
|
|
|
## Production
|
|
|
|
|
|
2019-05-08 16:37:45 +00:00
|
|
|
Argo CD supports several different ways in which Kubernetes manifests can be defined:
|
2018-07-27 23:51:44 +00:00
|
|
|
|
2019-05-08 16:37:45 +00:00
|
|
|
* [Kustomize](kustomize.md) applications
|
|
|
|
|
* [Helm](helm.md) charts
|
|
|
|
|
* [Ksonnet](ksonnet.md) applications
|
2019-10-21 23:54:23 +00:00
|
|
|
* A directory of YAML/JSON/Jsonnet manifests, including [Jsonnet](jsonnet.md).
|
2019-05-08 16:37:45 +00:00
|
|
|
* Any [custom config management tool](config-management-plugins.md) configured as a config management plugin
|
2019-06-18 17:03:19 +00:00
|
|
|
|
|
|
|
|
## Development
|
|
|
|
|
Argo CD also supports uploading local manifests directly. Since this is an anti-pattern of the
|
|
|
|
|
GitOps paradigm, this should only be done for development purposes. A user with an `override` permission is required
|
|
|
|
|
to upload manifests locally (typically an admin). All of the different Kubernetes deployment tools above are supported.
|
|
|
|
|
To upload a local application:
|
|
|
|
|
|
|
|
|
|
```bash
|
|
|
|
|
$ argocd app sync APPNAME --local /path/to/dir/
|
|
|
|
|
```
|
