|
3 | 3 | ## Table of Contents
|
4 | 4 | 1. [Installing OpenShift GitOps](#installing-openshift-gitops)
|
5 | 5 | 2. [Configure RHSSO for OpenShift GitOps(>= v1.2)](#configure-rhsso-for-openshift-gitops-v12)
|
6 |
| -3. [Setting up OpenShift Login (=< v1.1.2)](#setting-up-openshift-login--v112) |
7 |
| -4. [Configuring the groups claim](#configuring-the-groups-claim-) |
8 |
| -5. [Getting started with GitOps Application Manager (kam)](#getting-started-with-gitops-application-manager-kam) |
9 |
| -6. [Setting up a new ArgoCD instance](#setting-up-a-new-argo-cd-instance) |
10 |
| -7. [Configure resource quota/requests for OpenShift GitOps workloads](#configure-resource-quotarequests-for-openshift-gitops-workloads) |
11 |
| -8. [Running default Gitops workloads on Infrastructure Nodes](#running-default-gitops-workloads-on-infrastructure-nodes) |
12 |
| -9. [Monitoring](#monitoring) |
13 |
| -10. [Logging](#logging) |
14 |
| -11. [Prevent auto-reboot during Argo CD sync with machine configs](#prevent-auto-reboot-during-argo-cd-sync-with-machine-configs) |
15 |
| -12. [Machine configs and Argo CD: Performance challenges](#machine-configs-and-argo-cd-performance-challenges) |
16 |
| -13. [Health status of OpenShift resources](#health-status-of-openshift-resources) |
17 |
| -14. [Upgrade GitOps Operator from v1.0.1 to v1.1.0 (GA)](#upgrade-gitops-operator-from-v101-to-v110-ga) |
18 |
| -15. [Upgrade GitOps Operator from v1.1.2 to v1.2.0 (GA)](#upgrade-gitops-operator-from-v112-to-v120-ga) |
| 6 | +3. [Setting up OpenShift Login (=< v1.1.2)](#setting-up-openshift-login--v112) |
| 7 | +4. [Setting environment variables](#setting-environment-variables) |
| 8 | +5. [Configuring the groups claim](#configuring-the-groups-claim-) |
| 9 | +6. [Getting started with GitOps Application Manager (kam)](#getting-started-with-gitops-application-manager-kam) |
| 10 | +7. [Setting up a new ArgoCD instance](#setting-up-a-new-argo-cd-instance) |
| 11 | +8. [Configure resource quota/requests for OpenShift GitOps workloads](#configure-resource-quotarequests-for-openshift-gitops-workloads) |
| 12 | +9. [Running default Gitops workloads on Infrastructure Nodes](#running-default-gitops-workloads-on-infrastructure-nodes) |
| 13 | +10. [Monitoring](#monitoring) |
| 14 | +11. [Logging](#logging) |
| 15 | +12. [Prevent auto-reboot during Argo CD sync with machine configs](#prevent-auto-reboot-during-argo-cd-sync-with-machine-configs) |
| 16 | +13. [Machine configs and Argo CD: Performance challenges](#machine-configs-and-argo-cd-performance-challenges) |
| 17 | +14. [Health status of OpenShift resources](#health-status-of-openshift-resources) |
| 18 | +15. [Upgrade GitOps Operator from v1.0.1 to v1.1.0 (GA)](#upgrade-gitops-operator-from-v101-to-v110-ga) |
| 19 | +16. [Upgrade GitOps Operator from v1.1.2 to v1.2.0 (GA)](#upgrade-gitops-operator-from-v112-to-v120-ga) |
19 | 20 |
|
20 | 21 | ## Installing OpenShift GitOps
|
21 | 22 |
|
@@ -99,6 +100,8 @@ You can launch into this Argo CD instance from the Console Application Launcher.
|
99 | 100 |
|
100 | 101 | 
|
101 | 102 |
|
| 103 | +**Note: To disable the Link to Argo CD in the Console Application Launcher, see the documentation on how to disable consoleLink in the [setting environment variables section](#setting-environment-variables)** |
| 104 | + |
102 | 105 | Alternatively, the DNS hostname of the Argo CD Web Console can be retrieved by the command line.
|
103 | 106 |
|
104 | 107 | `oc get route openshift-gitops-server -n openshift-gitops -o jsonpath='{.spec.host}'`
|
@@ -412,6 +415,50 @@ Make sure to click **Save**. You should now have a new tab called **Credentials*
|
412 | 415 |
|
413 | 416 | 
|
414 | 417 |
|
| 418 | +## **Setting environment variables** |
| 419 | + |
| 420 | +Updating the following environment variables in the existing Subscription Object for the GitOps Operator will allow you (as an admin) to change certain properties in your cluster: |
| 421 | + |
| 422 | +<table> |
| 423 | + <tr> |
| 424 | + <td>Environment variable</td> |
| 425 | + <td>Default value</td> |
| 426 | + <td>Description</td> |
| 427 | + </tr> |
| 428 | + <tr> |
| 429 | + <td>ARGOCD_CLUSTER_CONFIG_NAMESPACES</td> |
| 430 | + <td>none</td> |
| 431 | + <td>When provided with a namespace, Argo CD is granted permissions to manage specific cluster-scoped resources which include |
| 432 | + platform operators, optional OLM operators, user management, etc. Argo CD is not granted cluster-admin.</td> |
| 433 | + </tr> |
| 434 | + <tr> |
| 435 | + <td>CONTROLLER_CLUSTER_ROLE</td> |
| 436 | + <td>none</td> |
| 437 | + <td>Administrators can configure a common cluster role for all the managed namespaces in role bindings for the Argo CD application controller with this environment variable. Note: If this environment variable contains custom roles, the Operator doesn't create the default admin role. Instead, it uses the existing custom role for all managed namespaces.</td> |
| 438 | + </tr> |
| 439 | + <tr> |
| 440 | + <td>DISABLE_DEFAULT_ARGOCD_CONSOLELINK</td> |
| 441 | + <td>false</td> |
| 442 | + <td>When set to `true`, will disable the ConsoleLink for Argo CD, which appears as the link to Argo CD in the Application Launcher. This can be beneficial to users of multi-tenant clusters who have multiple instances of Argo CD.</td> |
| 443 | + </tr> |
| 444 | + <tr> |
| 445 | + <td>DISABLE_DEFAULT_ARGOCD_INSTANCE</td> |
| 446 | + <td>false</td> |
| 447 | + <td>When set to `true`, will disable the default 'ready-to-use' installation of Argo CD in `openshift-gitops` namespace.</td> |
| 448 | + </tr> |
| 449 | + <tr> |
| 450 | + <td>DISABLE_DEX</td> |
| 451 | + <td>false</td> |
| 452 | + <td> When set to `true`, will remove the Dex deployment from the openshift-gitops namespace. Note: Disabling Dex will not be supported in v.1.9.0+. |
| 453 | + </td> |
| 454 | + </tr> |
| 455 | + <tr> |
| 456 | + <td>SERVER_CLUSTER_ROLE</td> |
| 457 | + <td>none</td> |
| 458 | + <td>Administrators can configure a common cluster role for all the managed namespaces in role bindings for the Argo CD server with this environment variable. Note: If this environment variable contains custom roles, the Operator doesn’t create the default admin role. Instead, it uses the existing custom role for all managed namespaces.</td> |
| 459 | + </tr> |
| 460 | +</table> |
| 461 | + |
415 | 462 | ## **Configuring the groups claim**[ ¶](https://argoproj.github.io/argo-cd/operator-manual/user-management/keycloak/#configuring-the-groups-claim)
|
416 | 463 |
|
417 | 464 | In order for Argo CD to provide the groups the user is in we need to configure a groups claim that can be included in the authentication token. To do this we'll start by creating a new **Client Scope** called *groups*.
|
@@ -562,7 +609,7 @@ data:
|
562 | 609 |
|
563 | 610 | ### Working with Dex
|
564 | 611 |
|
565 |
| -**NOTE:** For a fresh install of v1.3.0, Dex is automatically configured. You can log into the default Argo CD instance in the openshift-gitops namespace using the OpenShift or kubeadmin credentials. As an admin you can disable the Dex installation after the Operator is installed which will remove the Dex deployment from the openshift-gitops namespace. |
| 612 | +**NOTE:** As of v1.3.0, Dex is automatically configured. You can log into the default Argo CD instance in the openshift-gitops namespace using the OpenShift or kubeadmin credentials. As an admin you can disable the Dex installation after the Operator is installed which will remove the Dex deployment from the openshift-gitops namespace. |
566 | 613 |
|
567 | 614 | :warning: **DISABLE_DEX is Deprecated in OpenShift GitOps v1.6.0 and support will be removed in v1.9.0. Dex can be enabled/disabled by setting `.spec.sso.provider: dex` as follows:**
|
568 | 615 |
|
|
0 commit comments