Este conteúdo não está disponível no idioma selecionado.
Chapter 2. Argo CD custom resource and component properties
The ArgoCD
custom resource is a Kubernetes Custom Resource (CRD) that describes the desired state for a given Argo CD cluster that allows you to configure the components which make up an Argo CD cluster.
2.1. Argo CD CLI tool Copiar o linkLink copiado para a área de transferência!
The Argo CD CLI tool is a tool used to configure Argo CD through the command line. Red Hat OpenShift GitOps does not support this binary. Use the OpenShift Console to configure the Argo CD.
2.2. Argo CD custom resource properties Copiar o linkLink copiado para a área de transferência!
The Argo CD Custom Resource consists of the following properties:
Name | Description | Default | Properties |
|
The |
| |
|
|
|
|
| Add a configuration management plugin. |
| |
| Argo CD Application Controller options. |
|
|
| Disables the built-in admin user. |
| |
| Use a Google Analytics tracking ID. |
| |
| Enable hashed usernames sent to google analytics. |
| |
| High availablity options. |
|
|
| URL for getting chat help (this will typically be your Slack channel for support). | ||
| The text that appears in a text box for getting chat help. |
| |
|
The container image for all Argo CD components. This overrides the |
| |
| Ingress configuration options. |
| |
| Initial Git repositories to configure Argo CD to use upon creation of the cluster. |
| |
| Notifications controller configuration options. |
|
|
| Git repository credential templates to configure Argo CD to use upon creation of the cluster. |
| |
| Initial SSH Known Hosts for Argo CD to use upon creation of the cluster. |
| |
|
The build options and parameters to use with |
| |
| The OIDC configuration as an alternative to Dex. |
| |
|
Add the |
| |
| Prometheus configuration options. |
|
|
| RBAC configuration options. |
|
|
| Redis configuration options. |
|
|
| Customize resource behavior. |
| |
| Completely ignore entire classes of resource group. |
| |
| The configuration to configure which resource group/kinds are applied. |
| |
| Argo CD Server configuration options. |
|
|
| Single Sign-on options. |
|
|
| Enable application status badge. |
| |
| TLS configuration options. |
|
|
| Enable anonymous user access. |
| |
| The tag to use with the container image for all Argo CD components. | Latest Argo CD version | |
| Add a UI banner message. |
|
|
2.3. Repo server properties Copiar o linkLink copiado para a área de transferência!
The following properties are available for configuring the Repo server component:
Name | Default | Description |
|
| The container compute resources. |
|
|
Whether the |
|
|
The name of the |
|
| Whether to enforce strict TLS checking on all components when communicating with repo server. |
|
| Provider to use for setting up TLS the repo-server’s gRPC TLS certificate (one of: openshift). Currently only available for OpenShift. |
|
|
The container image for Argo CD Repo server. This overrides the |
|
same as | The tag to use with the Argo CD Repo server. |
|
| The log level used by the Argo CD Repo server. Valid options are debug, info, error, and warn. |
|
| The log format to be used by the Argo CD Repo server. Valid options are text or json. |
|
| Execution timeout in seconds for rendering tools (e.g. Helm, Kustomize). |
|
| Environment to set for the repository server workloads. |
|
|
The number of replicas for the Argo CD Repo server. Must be greater than or equal to |
2.4. Enabling notifications with Argo CD instance Copiar o linkLink copiado para a área de transferência!
To enable or disable the Argo CD notifications controller, set a parameter in the Argo CD custom resource. By default, notifications are disabled. To enable notifications, set the enabled
parameter to true
in the .yaml
file:
Procedure
-
Set the
enabled
parameter totrue
: