diff --git a/docs/assets/versions.js b/docs/assets/versions.js index c1a99d0287..08bd9e5903 100644 --- a/docs/assets/versions.js +++ b/docs/assets/versions.js @@ -140,9 +140,9 @@ window.addEventListener("DOMContentLoaded", function() { const currentVersion = getCurrentVersion(); if (currentVersion && currentVersion !== "stable") { if (currentVersion === "latest") { - document.querySelector("div[data-md-component=announce]").innerHTML = "
You are viewing the docs for an unreleased version of Argo CD, click here to go to the latest stable version.
"; + document.querySelector("div[data-md-component=announce]").innerHTML = "
You are viewing the docs for an unreleased version of Argo CD, view the latest stable version.
"; } else { - document.querySelector("div[data-md-component=announce]").innerHTML = "
You are viewing the docs for a previous version of Argo CD, click here to go to the latest stable version.
"; + document.querySelector("div[data-md-component=announce]").innerHTML = "
You are viewing the docs for a previous version of Argo CD, view the latest stable version.
"; } var bannerHeight = document.getElementById('announce-msg').offsetHeight + margin; document.querySelector("header.md-header").style.top = bannerHeight + "px"; diff --git a/docs/developer-guide/code-contributions.md b/docs/developer-guide/code-contributions.md index cee8993ae2..f6da32db69 100644 --- a/docs/developer-guide/code-contributions.md +++ b/docs/developer-guide/code-contributions.md @@ -96,9 +96,9 @@ Design documents are usually submitted as PR and use [this template](https://git ## Regular contributor meeting -Our community regularly meets virtually to discuss issues, ideas and enhancements around Argo CD. We do invite you to join this virtual meetings if you want to bring up certain things (including your enhancement proposals), participate in our triaging or just want to get to know other contributors. +Our community regularly meets virtually to discuss issues, ideas and enhancements around Argo CD. We do invite you to join this virtual meetings if you want to bring up certain things (including your enhancement proposals), participate in our triage, or just want to get to know other contributors. -The current cadence of our meetings is weekly, every Thursday at 8:15AM Pacific Time ([click here to check in your current timezone][1]). We use Zoom to conduct these meetings. +The current cadence of our meetings is weekly, every Thursday at 8:15AM Pacific Time ([convert to your current timezone][1]). We use Zoom to conduct these meetings. * [Agenda document (Google Docs, includes Zoom link)](https://docs.google.com/document/d/1xkoFkVviB70YBzSEa4bDnu-rUZ1sIFtwKKG1Uw8XsY8) diff --git a/docs/developer-guide/debugging-locally.md b/docs/developer-guide/debugging-locally.md index bc147e9443..ab122284a8 100644 --- a/docs/developer-guide/debugging-locally.md +++ b/docs/developer-guide/debugging-locally.md @@ -18,7 +18,7 @@ For the next steps, we will use Argo CD `api-server` as an example of running a ## Configure your IDE ### Locate your component configuration in `Procfile` -The `Procfile` is used by Goreman when running Argo CD locally with the local toolchain. The file is located in the top-level directory in your cloned Argo CD repo folder, you can view it's latest version [here](https://github.com/argoproj/argo-cd/blob/master/Procfile). It contains all the needed component run configuration, and you will need to copy parts of this configuration to your IDE. +The `Procfile` is used by Goreman when running Argo CD locally with the local toolchain. The [latest Procfile](https://github.com/argoproj/argo-cd/blob/master/Procfile) is located in the top-level directory in your cloned Argo CD repo folder. It contains all the needed component run configuration, and you will need to copy parts of this configuration to your IDE. Example for `api-server` configuration in `Procfile`: ``` text diff --git a/docs/developer-guide/faq.md b/docs/developer-guide/faq.md index 48c49e28e8..be246af00d 100644 --- a/docs/developer-guide/faq.md +++ b/docs/developer-guide/faq.md @@ -15,7 +15,7 @@ As we have limited resources, it can sometimes take a while for someone to respo ### How do I get my PR labeled `ready-for-review` ? -Conventionally an initial review is performed from a Argo member or reviewer. Once the initial review is approved, it can be labeled `ready-for-review` and then added to the [Argo CD Review](https://github.com/orgs/argoproj/projects/28) Github project. Details of the project dashboard can be found [here](https://github.com/orgs/argoproj/projects/28?pane=info). +Conventionally an initial review is performed from a Argo member or reviewer. Once the initial review is approved, it can be labeled `ready-for-review` and then added to the [Argo CD Review](https://github.com/orgs/argoproj/projects/28) Github project. The project dashboard provides a helpful [info panel](https://github.com/orgs/argoproj/projects/28?pane=info) on the review process. High quality reviews are extremely encouraged from the community. A member/reviewer may work with a community reviewer to get a PR labeled `ready-for-review`. It can then be added to the project dashboard and marked `Community Reviewed`. diff --git a/docs/developer-guide/running-locally.md b/docs/developer-guide/running-locally.md index fc39d0d127..8ef7cdfe8f 100644 --- a/docs/developer-guide/running-locally.md +++ b/docs/developer-guide/running-locally.md @@ -130,10 +130,11 @@ export ARGOCD_OPTS="--plaintext --insecure" #### Docs Changes -Modifying the docs auto-reloads the changes on the [documentation website](https://argo-cd.readthedocs.io/) that can be locally built using `make serve-docs-local` command. +The doc-site can be run in a container with `make serve-docs` or locally using `make serve-docs-local`. +When the doc-site process is run locally, modifying the docs will auto-reload changes in a preview of the [documentation website](https://argo-cd.readthedocs.io/). Once running, you can view your locally built documentation on port 8000. -Read more about this [here](https://argo-cd.readthedocs.io/en/latest/developer-guide/docs-site/). +The developer guide has detailed information about the [doc-site process](https://argo-cd.readthedocs.io/en/latest/developer-guide/docs-site/). #### UI Changes diff --git a/docs/faq.md b/docs/faq.md index cc99585a6a..fdb2685821 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -311,7 +311,7 @@ Argo CD default installation is now configured to automatically enable Redis aut If for some reason authenticated Redis does not work for you and you want to use non-authenticated Redis, here are the steps: 1. You need to have your own Redis installation. -2. Configure Argo CD to use your own Redis instance. See this [doc](https://argo-cd.readthedocs.io/en/stable/operator-manual/argocd-cmd-params-cm-yaml/) for the Argo CD configuration. +2. Configure Argo CD to use your own Redis instance, as shown in the [example configuration](operator-manual/argocd-cmd-params-cm-yaml.md). 3. If you already installed Redis shipped with Argo CD, you also need to clean up the existing components: * When HA Redis is used: diff --git a/docs/index.md b/docs/index.md index 534e0dd503..5683d401fa 100644 --- a/docs/index.md +++ b/docs/index.md @@ -87,8 +87,8 @@ For additional details, see [architecture overview](operator-manual/architecture ## Development Status -Argo CD is being actively developed by the community. Our releases can be found [here](https://github.com/argoproj/argo-cd/releases). +Argo CD is being actively developed by the community. [Releases](https://github.com/argoproj/argo-cd/releases) are listed on Github. ## Adoption -Organizations who have officially adopted Argo CD can be found [here](https://github.com/argoproj/argo-cd/blob/master/USERS.md). +A growing list of organizations(https://github.com/argoproj/argo-cd/blob/master/USERS.md) have officially adopted Argo CD. diff --git a/docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md b/docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md index 106a567b6a..bb2d86f8ce 100644 --- a/docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md +++ b/docs/operator-manual/applicationset/Generators-Cluster-Decision-Resource.md @@ -70,7 +70,7 @@ data: matchKey: clusterName ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/clusterDecisionResource).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/clusterDecisionResource)*) This example leverages the cluster management capabilities of the [open-cluster-management.io community](https://open-cluster-management.io/). By creating a `ConfigMap` with the GVK for the `open-cluster-management.io` Placement rule, your ApplicationSet can provision to different clusters in a number of novel ways. One example is to have the ApplicationSet maintain only two Argo CD Applications across 3 or more clusters. Then as maintenance or outages occur, the ApplicationSet will always maintain two Applications, moving the application to available clusters under the Placement rule's direction. diff --git a/docs/operator-manual/applicationset/Generators-Cluster.md b/docs/operator-manual/applicationset/Generators-Cluster.md index a29e32e735..1e52088c5f 100644 --- a/docs/operator-manual/applicationset/Generators-Cluster.md +++ b/docs/operator-manual/applicationset/Generators-Cluster.md @@ -57,9 +57,9 @@ spec: server: '{{.server}}' # 'server' field of the secret namespace: guestbook ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/cluster).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/cluster).*) -In this example, the cluster secret's `name` and `server` fields are used to populate the `Application` resource `name` and `server` (which are then used to target that same cluster). +In this example, the cluster secret's `name` and `server` fields are used to populate the `Application` resource `name` and `server`, which are then used to target that same cluster. ### Label selector diff --git a/docs/operator-manual/applicationset/Generators-Git-File-Globbing.md b/docs/operator-manual/applicationset/Generators-Git-File-Globbing.md index 04efabeceb..faa39e5596 100644 --- a/docs/operator-manual/applicationset/Generators-Git-File-Globbing.md +++ b/docs/operator-manual/applicationset/Generators-Git-File-Globbing.md @@ -59,7 +59,7 @@ Note that the default may change in the future. ## Usage -The new Git file generator globbing uses the `doublestar` package. You can find it [here](https://github.com/bmatcuk/doublestar). +The new Git file generator globbing uses the [doublestar package](https://github.com/bmatcuk/doublestar). Below is a short excerpt from its documentation. diff --git a/docs/operator-manual/applicationset/Generators-Git.md b/docs/operator-manual/applicationset/Generators-Git.md index 0d51d0b2f6..fd57c5da47 100644 --- a/docs/operator-manual/applicationset/Generators-Git.md +++ b/docs/operator-manual/applicationset/Generators-Git.md @@ -63,7 +63,7 @@ spec: syncOptions: - CreateNamespace=true ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-directory).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-directory).*) The generator parameters are: @@ -72,9 +72,13 @@ The generator parameters are: - `{{.path.basename}}`: For any directory path within the Git repository that matches the `path` wildcard, the right-most path name is extracted (e.g. `/directory/directory2` would produce `directory2`). - `{{.path.basenameNormalized}}`: This field is the same as `path.basename` with unsupported characters replaced with `-` (e.g. a `path` of `/directory/directory_2`, and `path.basename` of `directory_2` would produce `directory-2` here). -**Note**: The right-most path name always becomes `{{.path.basename}}`. For example, for `- path: /one/two/three/four`, `{{.path.basename}}` is `four`. +> [!NOTE] +> The right-most path name always becomes `{{.path.basename}}`. For example, for `- path: /one/two/three/four`, `{{.path.basename}}` is `four`. -**Note**: If the `pathParamPrefix` option is specified, all `path`-related parameter names above will be prefixed with the specified value and a dot separator. E.g., if `pathParamPrefix` is `myRepo`, then the generated parameter name would be `.myRepo.path` instead of `.path`. Using this option is necessary in a Matrix generator where both child generators are Git generators (to avoid conflicts when merging the child generators’ items). +> [!NOTE] +> If the `pathParamPrefix` option is specified, all `path`-related parameter names above will be prefixed with the specified value and a dot separator. +> E.g., if `pathParamPrefix` is `myRepo`, then the generated parameter name would be `.myRepo.path` instead of `.path`. Using this option is necessary +> in a Matrix generator where both child generators are Git generators (to avoid conflicts when merging the child generators’ items). Whenever a new Helm chart/Kustomize YAML/Application/plain subdirectory is added to the Git repository, the ApplicationSet controller will detect this change and automatically deploy the resulting manifests within new `Application` resources. @@ -116,7 +120,7 @@ spec: server: https://kubernetes.default.svc namespace: '{{.path.basename}}' ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-directory/excludes).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-directory/excludes).*) This example excludes the `exclude-helm-guestbook` directory from the list of directories scanned for this `ApplicationSet` resource. @@ -320,7 +324,7 @@ spec: server: '{{.cluster.address}}' namespace: guestbook ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-files-discovery).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-files-discovery).*) Any `config.json` files found under the `cluster-config` directory will be parameterized based on the `path` wildcard pattern specified. Within each file JSON fields are flattened into key/value pairs, with this ApplicationSet example using the `cluster.address` and `cluster.name` parameters in the template. @@ -335,12 +339,18 @@ In addition to the flattened key/value pairs from the configuration file, the fo - `{{.path.filename}}`: The matched filename. e.g., `config.json` in the above example. - `{{.path.filenameNormalized}}`: The matched filename with unsupported characters replaced with `-`. -**Note**: The right-most *directory* name always becomes `{{.path.basename}}`. For example, from `- path: /one/two/three/four/config.json`, `{{.path.basename}}` will be `four`. -The filename can always be accessed using `{{.path.filename}}`. +> [!NOTE] +> The right-most *directory* name always becomes `{{.path.basename}}`. For example, from `- path: /one/two/three/four/config.json`, `{{.path.basename}}` +> will be `four`. The filename can always be accessed using `{{.path.filename}}`. -**Note**: If the `pathParamPrefix` option is specified, all `path`-related parameter names above will be prefixed with the specified value and a dot separator. E.g., if `pathParamPrefix` is `myRepo`, then the generated parameter name would be `myRepo.path` instead of `path`. Using this option is necessary in a Matrix generator where both child generators are Git generators (to avoid conflicts when merging the child generators’ items). +> [!NOTE] +> If the `pathParamPrefix` option is specified, all `path`-related parameter names above will be prefixed with the specified value and a dot separator. +> E.g., if `pathParamPrefix` is `myRepo`, then the generated parameter name would be `myRepo.path` instead of `path`. Using this option is necessary +> in a Matrix generator where both child generators are Git generators (to avoid conflicts when merging the child generators’ items). -**Note**: The default behavior of the Git file generator is very greedy. Please see [Git File Generator Globbing](./Generators-Git-File-Globbing.md) for more information. +> [!NOTE] +> The default behavior of the Git file generator is very greedy. +> Please see [Git File Generator Globbing](./Generators-Git-File-Globbing.md) for more information. ### Exclude files @@ -379,7 +389,7 @@ spec: This example excludes the `config.json` file in the `dev` directory from the list of files scanned for this `ApplicationSet` resource. -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-files-discovery/excludes).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/git-generator-files-discovery/excludes).*) ### Pass additional key-value pairs via `values` field @@ -476,7 +486,7 @@ spec: ``` > [!NOTE] -> The ApplicationSet controller webhook does not use the same webhook as the API server as defined [here](../webhook.md). ApplicationSet exposes a webhook server as a service of type ClusterIP. An ApplicationSet specific Ingress resource needs to be created to expose this service to the webhook source. +> The ApplicationSet controller webhook does not use the same [API server webhook](../webhook.md). ApplicationSet exposes a webhook server as a service of type ClusterIP. An ApplicationSet specific Ingress resource needs to be created to expose this service to the webhook source. ### 1. Create the webhook in the Git provider diff --git a/docs/operator-manual/applicationset/Generators-List.md b/docs/operator-manual/applicationset/Generators-List.md index 5a706d2239..30863d6d83 100644 --- a/docs/operator-manual/applicationset/Generators-List.md +++ b/docs/operator-manual/applicationset/Generators-List.md @@ -30,7 +30,7 @@ spec: server: '{{.url}}' namespace: guestbook ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/list-generator).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/list-generator).*) In this example, the List generator passes the `url` and `cluster` fields as parameters into the template. If we wanted to add a second environment, we could uncomment the second element and the ApplicationSet controller would automatically target it with the defined application. diff --git a/docs/operator-manual/applicationset/Generators-Matrix.md b/docs/operator-manual/applicationset/Generators-Matrix.md index 077157544c..d79f033538 100644 --- a/docs/operator-manual/applicationset/Generators-Matrix.md +++ b/docs/operator-manual/applicationset/Generators-Matrix.md @@ -106,7 +106,7 @@ Finally, the Matrix generator will combine both sets of outputs, and produce: path: /examples/git-generator-directory/cluster-addons/prometheus-operator path.basename: prometheus-operator ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/matrix).*) +(*The [full example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/matrix).*) ## Using Parameters from one child generator in another child generator diff --git a/docs/operator-manual/applicationset/Generators-Pull-Request.md b/docs/operator-manual/applicationset/Generators-Pull-Request.md index c0dc1b347b..98f902e4c2 100644 --- a/docs/operator-manual/applicationset/Generators-Pull-Request.md +++ b/docs/operator-manual/applicationset/Generators-Pull-Request.md @@ -454,7 +454,7 @@ When using a Pull Request generator, the ApplicationSet controller polls every ` The configuration is almost the same as the one described [in the Git generator](Generators-Git.md), but there is one difference: if you want to use the Pull Request Generator as well, additionally configure the following settings. > [!NOTE] -> The ApplicationSet controller webhook does not use the same webhook as the API server as defined [here](../webhook.md). ApplicationSet exposes a webhook server as a service of type ClusterIP. An ApplicationSet specific Ingress resource needs to be created to expose this service to the webhook source. +> The ApplicationSet controller webhook does not use the same [API server webhook](../webhook.md). ApplicationSet exposes a webhook server as a service of type ClusterIP. An ApplicationSet specific Ingress resource needs to be created to expose this service to the webhook source. ### Github webhook configuration diff --git a/docs/operator-manual/applicationset/Template.md b/docs/operator-manual/applicationset/Template.md index bce8c6487f..17914c7e4a 100644 --- a/docs/operator-manual/applicationset/Template.md +++ b/docs/operator-manual/applicationset/Template.md @@ -124,9 +124,8 @@ spec: server: '{{ .server }}' namespace: guestbook ``` -(*The full example can be found [here](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/template-override).*) -In this example, the ApplicationSet controller will generate an `Application` resource using the `path` generated by the List generator, rather than the `path` value defined in `.spec.template`. +In [this example](https://github.com/argoproj/argo-cd/tree/master/applicationset/examples/template-override), the ApplicationSet controller will generate an `Application` resource using the `path` generated by the List generator, rather than the `path` value defined in `.spec.template`. ## Template Patch diff --git a/docs/operator-manual/installation.md b/docs/operator-manual/installation.md index 869210e650..e8b7eb3331 100644 --- a/docs/operator-manual/installation.md +++ b/docs/operator-manual/installation.md @@ -7,8 +7,7 @@ Argo CD has two type of installations: multi-tenant and core. The multi-tenant installation is the most common way to install Argo CD. This type of installation is typically used to service multiple application developer teams in the organization and maintained by a platform team. -The end-users can access Argo CD via the API server using the Web UI or `argocd` CLI. The `argocd` CLI has to be configured using `argocd login ` command -(learn more [here](../user-guide/commands/argocd_login.md)). +The end-users can access Argo CD via the API server using the Web UI or `argocd` CLI. The `argocd` CLI has to be [configured](../user-guide/commands/argocd_login.md) using `argocd login ` command. Two types of installation manifests are provided: @@ -118,7 +117,7 @@ The Argo CD can be installed using [Helm](https://helm.sh/). The Helm chart is c ## Supported versions -For detailed information regarding Argo CD's version support policy, please refer to the [Release Process and Cadence documentation](https://argo-cd.readthedocs.io/en/stable/developer-guide/release-process-and-cadence/). +For detailed information regarding Argo CD's version support policy, please refer to the [Release Process and Cadence documentation](../developer-guide/release-process-and-cadence.md). ## Tested versions diff --git a/docs/operator-manual/metrics.md b/docs/operator-manual/metrics.md index 927b42a8da..9b3ebcaaf9 100644 --- a/docs/operator-manual/metrics.md +++ b/docs/operator-manual/metrics.md @@ -416,7 +416,7 @@ spec: ## Dashboards -You can find an example Grafana dashboard [here](https://github.com/argoproj/argo-cd/blob/master/examples/dashboard.json) or check demo instance +You can find an [example Grafana dashboard](https://github.com/argoproj/argo-cd/blob/master/examples/dashboard.json) or check the demo instance [dashboard](https://grafana.apps.argoproj.io). ![dashboard](../assets/dashboard.jpg) diff --git a/docs/operator-manual/upgrading/1.8-2.0.md b/docs/operator-manual/upgrading/1.8-2.0.md index 2d1b0b3a20..3ba3d356c1 100644 --- a/docs/operator-manual/upgrading/1.8-2.0.md +++ b/docs/operator-manual/upgrading/1.8-2.0.md @@ -117,8 +117,7 @@ Helm adds). You can fix this by syncing the Application. If you have existing Charts that require to be rendered using Helm v2, you will need to explicitly configure your Application to use Helm v2 for rendering the -chart, as described -[here](../../user-guide/helm.md#helm-version). +chart, as described in the user guide's section on [Helm](../../user-guide/helm.md#helm-version). Please also note that Helm v2 is now being considered deprecated in Argo CD, as it will not receive any updates from the upstream Helm project anymore. We will diff --git a/docs/try_argo_cd_locally.md b/docs/try_argo_cd_locally.md index ee88dbcfba..342342a1d5 100644 --- a/docs/try_argo_cd_locally.md +++ b/docs/try_argo_cd_locally.md @@ -10,7 +10,7 @@ To run an Argo CD development environment review the [developer guide for runnin ## Install Kind -Install Kind Following Instructions [here](https://kind.sigs.k8s.io/docs/user/quick-start#installation). +Install Kind following their quick-start [instructions](https://kind.sigs.k8s.io/docs/user/quick-start#installation). ## Create a Kind Cluster Once Kind is installed, create a new Kubernetes cluster with: diff --git a/docs/user-guide/auto_sync.md b/docs/user-guide/auto_sync.md index 645095a590..c2eeb49f77 100644 --- a/docs/user-guide/auto_sync.md +++ b/docs/user-guide/auto_sync.md @@ -32,7 +32,7 @@ spec: ## Temporarily toggling auto-sync for applications managed by ApplicationSets For a standalone application, toggling auto-sync is performed by changing the application's `spec.syncPolicy.automated` field. For an ApplicationSet managed application, changing the application's `spec.syncPolicy.automated` field will, however, have no effect. -Read more details about how to perform the toggling for applications managed by ApplicationSets [here](../operator-manual/applicationset/Controlling-Resource-Modification.md). +[Controlling Resource Modification](../operator-manual/applicationset/Controlling-Resource-Modification.md) has more details about how to perform the toggling for applications managed by ApplicationSets. ## Automatic Pruning diff --git a/docs/user-guide/helm.md b/docs/user-guide/helm.md index 540f893ad7..541be95e1d 100644 --- a/docs/user-guide/helm.md +++ b/docs/user-guide/helm.md @@ -45,9 +45,9 @@ spec: > [!NOTE] > **When using Helm there are multiple ways to provide values** > -> Order of precedence is `parameters > valuesObject > values > valueFiles > helm repository values.yaml` (see [Here](./helm.md#helm-value-precedence) for a more detailed example) +> Order of precedence is `parameters > valuesObject > values > valueFiles > helm repository values.yaml`. [Value precedence](./helm.md#helm-value-precedence) has a more detailed example. -See [here](../operator-manual/declarative-setup.md#helm) for more info about how to configure private Helm repositories and private OCI registries. +The [Declarative Setup section on Helm](../operator-manual/declarative-setup.md#helm) has more info about how to configure private Helm repositories and private OCI registries. ## Values Files diff --git a/docs/user-guide/sync-options.md b/docs/user-guide/sync-options.md index 56ccb00ad5..f58dd66823 100644 --- a/docs/user-guide/sync-options.md +++ b/docs/user-guide/sync-options.md @@ -139,7 +139,7 @@ $ argocd app set guestbook --sync-option ApplyOutOfSyncOnly=true By default, extraneous resources get pruned using the foreground deletion policy. The propagation policy can be controlled using the `PrunePropagationPolicy` sync option. Supported policies are background, foreground, and orphan. -More information about those policies can be found [here](https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/#controlling-how-the-garbage-collector-deletes-dependents). +More information about those policies can be found in the Kubernetes [Garbage Collection](https://kubernetes.io/docs/concepts/workloads/controllers/garbage-collection/) documentation. ```yaml apiVersion: argoproj.io/v1alpha1