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

Fix broken note on CLI validation page 

This also takes the opportunity to rename files for consistency in URLs,
all lowercase.
This commit is contained in:
Corentin Néau 2025-10-14 09:37:33 +02:00
parent b14d9bc122
commit 0040d493e3
No known key found for this signature in database
GPG Key ID: 4E10825BFE040608
6 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/bundle-add.md
View File

@ -89,5 +89,5 @@ You can't use a `fleet.yaml` in resources, it is only used by the fleet-cli to c
The `spec.targetRestrictions` field is not useful, as it is an allow list for targets specified in `spec.targets`. It is not needed, since `targets` are explicitly given in a bundle and an empty `targetRestrictions` defaults to allow. The `spec.targetRestrictions` field is not useful, as it is an allow list for targets specified in `spec.targets`. It is not needed, since `targets` are explicitly given in a bundle and an empty `targetRestrictions` defaults to allow.
:::note :::note
You can use Fleet CLI to convert a Helm chart into a `bundle`. For more information, refer to [Convert a Helm chart into a bundle using CLI.](install-usage-fleetCLI.md#convert-a-helm-chart-into-a-bundle). You can use Fleet CLI to convert a Helm chart into a `bundle`. For more information, refer to [Convert a Helm chart into a bundle using CLI.](install-usage-fleet-cli.md#convert-a-helm-chart-into-a-bundle).
::: :::

0
docs/install-usage-fleetCLI.md → docs/install-usage-fleet-cli.md
View File

2
docs/ref-bundle-stages.md
View File

@ -59,4 +59,4 @@ fleet target --bundle-file bundle.yaml --dump-input-list > bd.yaml
fleet deploy --input-file bd.yaml --dry-run fleet deploy --input-file bd.yaml --dry-run
``` ```
For more information, refer to [Fleet CLI Key commands.](install-usage-fleetCLI.md#key-commands) For more information, refer to [Fleet CLI Key commands.](install-usage-fleet-cli.md#key-commands)

2
docs/ref-fleet-yaml.md
View File

@ -449,7 +449,7 @@ avoid conflicts with other templating languages.
Note that if the functions output changes with every call, e.g. `uuidv4`, the Note that if the functions output changes with every call, e.g. `uuidv4`, the
bundle will get redeployed. bundle will get redeployed.
You can [test values templating with the CLI](./install-usage-fleetCLI.md#key-commands) against existing clusters. You can [test values templating with the CLI](./install-usage-fleet-cli.md#key-commands) against existing clusters.
The template context has the following keys: The template context has the following keys:

2
docs/validate-fleetCLI.md → docs/validate-fleet-cli.md
View File

@ -21,7 +21,7 @@ You see the following fields:
* `BUNDLEDEPLOYMENTS-READY` shows how many targets are ready out of the total. * `BUNDLEDEPLOYMENTS-READY` shows how many targets are ready out of the total.
* `STATUS` may show Ready, Modified, or other conditions based on the `rollout`. * `STATUS` may show Ready, Modified, or other conditions based on the `rollout`.
:::note: :::note
If this field shows 1/1, the bundle is successfully deployed to one cluster. If this field shows 1/1, the bundle is successfully deployed to one cluster.
::: :::

4
sidebars.js
View File

@ -9,8 +9,8 @@ module.exports = {
items:[ items:[
'quickstart', 'quickstart',
'tut-deployment', 'tut-deployment',
'install-usage-fleetCLI', 'install-usage-fleet-cli',
'validate-fleetCLI', 'validate-fleet-cli',
{type:'doc', id:'uninstall'}, {type:'doc', id:'uninstall'},
], ],
}, },