Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos in argo-cd-crossplane.md #663

Merged
merged 1 commit into from
Dec 29, 2023
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions content/knowledge-base/integrations/argo-cd-crossplane.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ to use Annotation based resource tracking. See the [Argo CD docs](https://argo-c

#### Set Resource Tracking Method

In oder for Argo CD to correctly track an Application resources that contain Crossplane related object it needs
In order for Argo CD to correctly track Application resources that contain Crossplane related objects it needs
to be configured to use the annotation mechanism.

To configure it, edit the `argocd-cm` `ConfigMap` in the `argocd` `Namespace` as such:
Expand All @@ -37,7 +37,7 @@ in Argo's [repository](https://github.com/argoproj/argo-cd/tree/master/resource_
from `pkg.crossplane.io` has already been declared which means there no further configuration needed.

Argo CD also enable customising these checks per instance, and that's the mechanism used to provide support
of Provider's CRDs
of Provider's CRDs.

To configure it, edit the `argocd-cm` `ConfigMap` in the `argocd` `Namespace` as such:
```yaml
Expand Down Expand Up @@ -128,8 +128,8 @@ data:
#### Set Resource Exclusion

Crossplane providers generates a `ProviderConfigUsage` for each of the managed resource (MR) it handles. This resource
enable representing the relationship between MR and a ProviderConfig so that controller can use it as finalizer when a
ProviderConfig is deleted. End-user of Crossplane are not expected to interact with this resource.
enable representing the relationship between MR and a ProviderConfig so that the controller can use it as finalizer when a
ProviderConfig is deleted. End-users of Crossplane are not expected to interact with this resource.

Argo CD UI reactivity can be impacted as the number of resource and types grow. To help keep this number low we
recommend hiding all `ProviderConfigUsage` resources from Argo CD UI.
Expand Down
Loading