destination reference to the target cluster and namespace.source reference to the desired state in Git (repository, revision, path, environment).It is defined by two key pieces of information: The Application CRD is the Kubernetes resource object representing a deployed application instance This also means that application and project names are unique within a given Argo CD installation - you cannot have the same application name for two different applications. Multiple configuration objects ¶ Sample Fileįor Application and AppProject resources, the name of the resource equals the name of the application or project within Argo CD. SSH known hosts data for connecting Git repositories via SSH (v1.2 and later)įor each specific kind of ConfigMap and Secret resource, there is only a single supported resource name (as listed in the above table) - if you need to merge things you need to do it before creating them.īe sure to annotate your ConfigMap resources using the label /part-of: argocd, otherwise Argo CD will not be able to use them. User Passwords, Certificates (deprecated), Signing Key, Dex secrets, Webhook secretsĬustom TLS certificates for connecting Git repositories via HTTPS (v1.2 and later) My-private-repo / istio-helm-repo / private-helm-repo / private-repoĪrgoproj-https-creds / argoproj-ssh-creds / github-creds / github-enterprise-creds

Quick Reference ¶Īll resources, including Application and AppProject specs, have to be installed in the Argo CD namespace (by default argocd). These can be updated using kubectl apply, without needing to touch the argocd command-line tool. Generating Applications with ApplicationSetĪrgo CD applications, projects and settings can be defined declaratively using Kubernetes manifests. How ApplicationSet controller interacts with Argo CD

Repositories using self-signed TLS certificates (or are signed by custom CA)

Mattermost github