crossplane
/
docs
mirror of https://github.com/crossplane/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Fix unintended paragraph breaks 

This moves HTML comments out of paragraphs because they're creating
breaks.

Signed-off-by: Branden Rolston <branden@upbound.io>
This commit is contained in:
Branden Rolston 2025-09-04 13:35:00 -07:00
parent 728557b30f
commit e5bb91d8a0
No known key found for this signature in database
GPG Key ID: 5F330CEFBF06AFE5
2 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
content/master/packages/providers.md
View File

@ -684,28 +684,28 @@ package runtime container.
<!-- vale write-good.Passive = NO -->
The package manager is opinionated about some fields to ensure
<!-- vale write-good.Passive = YES -->
the runtime is working and overlay them on top of the values
in the runtime configuration. For example, it defaults the replica count
to 1 if not set and overrides the label selectors to make sure the Deployment
and Service match. It also injects any necessary environment variables,
ports and volumes and volume mounts.
<!-- vale write-good.Passive = YES -->
<!-- vale gitlab.FutureTense = NO -->
The `Provider` or `Functions`'s `spec.runtimeConfigRef.name` field defaults
to value `default`, which means Crossplane uses the default runtime configuration
if not specified. Crossplane ensures there is always a default runtime
<!-- vale gitlab.FutureTense = NO -->
configuration in the cluster, but won't change it if it already exists. This
<!-- vale gitlab.FutureTense = YES -->
allows users to customize the default runtime configuration to their needs.
<!-- vale gitlab.FutureTense = YES -->
{{<hint "tip" >}}
<!-- vale gitlab.SubstitutionWarning = NO -->
Since `DeploymentRuntimeConfig` uses the same schema as Kubernetes `Deployment`
<!-- vale gitlab.SubstitutionWarning = YES -->
spec, you may need to pass empty values to bypass the schema validation.
For example, if you just want to change the `replicas` field, you would
need to pass the following:
<!-- vale gitlab.SubstitutionWarning = YES -->
```yaml
apiVersion: pkg.crossplane.io/v1beta1

8
content/v2.0/packages/providers.md
View File

@ -684,28 +684,28 @@ package runtime container.
<!-- vale write-good.Passive = NO -->
The package manager is opinionated about some fields to ensure
<!-- vale write-good.Passive = YES -->
the runtime is working and overlay them on top of the values
in the runtime configuration. For example, it defaults the replica count
to 1 if not set and overrides the label selectors to make sure the Deployment
and Service match. It also injects any necessary environment variables,
ports and volumes and volume mounts.
<!-- vale write-good.Passive = YES -->
<!-- vale gitlab.FutureTense = NO -->
The `Provider` or `Functions`'s `spec.runtimeConfigRef.name` field defaults
to value `default`, which means Crossplane uses the default runtime configuration
if not specified. Crossplane ensures there is always a default runtime
<!-- vale gitlab.FutureTense = NO -->
configuration in the cluster, but won't change it if it already exists. This
<!-- vale gitlab.FutureTense = YES -->
allows users to customize the default runtime configuration to their needs.
<!-- vale gitlab.FutureTense = YES -->
{{<hint "tip" >}}
<!-- vale gitlab.SubstitutionWarning = NO -->
Since `DeploymentRuntimeConfig` uses the same schema as Kubernetes `Deployment`
<!-- vale gitlab.SubstitutionWarning = YES -->
spec, you may need to pass empty values to bypass the schema validation.
For example, if you just want to change the `replicas` field, you would
need to pass the following:
<!-- vale gitlab.SubstitutionWarning = YES -->
```yaml
apiVersion: pkg.crossplane.io/v1beta1