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 links for 0.13 

Static images are referenced through relative paths, which needed to be
adjusted.
This commit is contained in:
Corentin Néau 2025-07-24 16:01:32 +02:00
parent 47badcb2e5
commit 62465537ad
No known key found for this signature in database
GPG Key ID: 4E10825BFE040608
2 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
versioned_docs/version-0.13/oci-storage.md
View File

@ -11,7 +11,7 @@ Using an OCI registry helps you:
* Reduce etcd load by offloading large bundle content.
* Use a standardized storage backend for large manifests or Helm charts.
![A visual asset displaying the flow of Fleet with OCI Storage.](../static/img/fleet-ociStorage-flow.png)
![A visual asset displaying the flow of Fleet with OCI Storage.](../../static/img/fleet-ociStorage-flow.png)
:::note
Fleet checks for the integrity of OCI artifacts and Fleet tags OCI artifact as `latest`.
@ -117,4 +117,4 @@ To decrypt your secret, you can run:
`kubectl get secret ocistorage -n fleet-local -o json | jq '.data | map_values(@base64d)`
![A screenshot of OCI secrets enabled for Fleet](../static/img/ociStorage-secret-ss.png)
![A screenshot of OCI secrets enabled for Fleet](../../static/img/ociStorage-secret-ss.png)

10
versioned_docs/version-0.13/rollout.md
View File

@ -43,7 +43,7 @@ Fleet rolls out deployments in batches of up to 50 clusters per partition, regar
The following diagram displays how Fleet handles rollout:
![A visual asset displaying flow of rollout in Fleet.](../static/img/flow-rollout-fleet.png)
![A visual asset displaying flow of rollout in Fleet.](../../static/img/flow-rollout-fleet.png)
Various limits that can be configured in Fleet:
@ -93,7 +93,7 @@ Fleet then:
The following diagram illustrates how Fleet handles rollout across multiple partitions, including readiness checks and deployment flow:
![A visual asset displaying the flow of partition rollout](../static/img/deploy-targets-partition.png)
![A visual asset displaying the flow of partition rollout](../../static/img/deploy-targets-partition.png)
:::note
MaxNew is always 50. A bundle change can only stage 50 `BundleDeployments` at a time.
@ -101,7 +101,7 @@ MaxNew is always 50. A bundle change can only stage 50 `BundleDeployments` at a
Within each partition, Fleet rolls out up to 50 `BundleDeployments` at a time. The diagram below shows how Fleet determines whether to proceed or wait during this process:
![A visual asset displaying the flow of deploying targets in a partition](../static/img/partition-rollout-flow.png)
![A visual asset displaying the flow of deploying targets in a partition](../../static/img/partition-rollout-flow.png)
:::note
Fleet recommends labeling clusters so you can use those labels to assign clusters to specific partitions.
@ -177,7 +177,7 @@ rolloutStrategy:
The following diagram illustrates how Fleet handles 50 clusters in a single partition:
![A visual asset displaying 50 clusters](../static/img/deploy-50Clusters.png)
![A visual asset displaying 50 clusters](../../static/img/deploy-50Clusters.png)
### Scenario: 100 Clusters (Single Partition)
@ -233,7 +233,7 @@ rolloutStrategy:
The following diagram describes how Fleet handles whether to continue or pause rollout.
![A visual asset displaying the partitions about rollout in Fleet](../static/img/partition-fleet-rollout.png)
![A visual asset displaying the partitions about rollout in Fleet](../../static/img/partition-fleet-rollout.png)
This ensures full readiness and staged rollout across all 200 clusters. Use this approach when you need precise rollout sequencing and full cluster readiness before advancing.