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

Updates fleet repository links after moving to main 

This PR should be merged after https://github.com/rancher/fleet/pull/2240

It replaces all `fleet` repo references from `master` to `main`

Refers to: https://github.com/rancher/fleet/issues/2234

Signed-off-by: Xavi Garcia <xavi.garcia@suse.com>
This commit is contained in:
Xavi Garcia 2024-03-20 13:12:07 +01:00
parent 3eaf241c9d
commit 97f9203d07
6 changed files with 26 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/ref-configuration.md
View File

@ -6,9 +6,9 @@ A reference list of, mostly internal, configuration options.
The Helm charts accept, at least, the options as shown with their default in `values.yaml`:
* https://github.com/rancher/fleet/blob/master/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-agent/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-agent/values.yaml
## Environment Variables
@ -16,13 +16,13 @@ The controllers can be started with these environment variables:
* `CATTLE_DEV_MODE` - used to debug wrangler, not usable
* `FLEET_CLUSTER_ENQUEUE_DELAY` - tune how often non-ready clusters are checked
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/master/docs/performance.md)
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/main/docs/performance.md)
## Configuration
In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.
The config [struct](https://github.com/rancher/fleet/blob/master/pkg/config/config.go#L40-L52) is used in both config maps:
The config [struct](https://github.com/rancher/fleet/blob/main/pkg/config/config.go#L40-L52) is used in both config maps:
* cattle-fleet-system/fleet-agent
* cattle-fleet-system/fleet-controller

10
versioned_docs/version-0.6/ref-configuration.md
View File

@ -6,9 +6,9 @@ A reference list of, mostly internal, configuration options.
The Helm charts accept, at least, the options as shown with their default in `values.yaml`:
* https://github.com/rancher/fleet/blob/master/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-agent/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-agent/values.yaml
## Environment Variables
@ -16,13 +16,13 @@ The controllers can be started with these environment variables:
* `CATTLE_DEV_MODE` - used to debug wrangler, not usable
* `FLEET_CLUSTER_ENQUEUE_DELAY` - tune how often non-ready clusters are checked
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/master/docs/performance.md)
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/main/docs/performance.md)
## Configuration
In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.
The config [struct](https://github.com/rancher/fleet/blob/master/pkg/config/config.go#L40-L52) is used in both config maps:
The config [struct](https://github.com/rancher/fleet/blob/main/pkg/config/config.go#L40-L52) is used in both config maps:
* cattle-fleet-system/fleet-agent
* cattle-fleet-system/fleet-controller

2
versioned_docs/version-0.6/ref-fleet-yaml.md
View File

@ -4,7 +4,7 @@ The `fleet.yaml` file adds options to a bundle. Any directory with a `fleet.yaml
For more information on how to use the `fleet.yaml` to customize bundles see [Git Repository Contents](./gitrepo-content.md).
The content of the fleet.yaml corresponds to https://github.com/rancher/fleet/blob/master/pkg/bundlereader/read.go#L129-L135, which contains the [BundleSpec](./ref-crds#bundlespec).
The content of the fleet.yaml corresponds to https://github.com/rancher/fleet/blob/main/pkg/bundlereader/read.go#L129-L135, which contains the [BundleSpec](./ref-crds#bundlespec).
### Reference

10
versioned_docs/version-0.7/ref-configuration.md
View File

@ -6,9 +6,9 @@ A reference list of, mostly internal, configuration options.
The Helm charts accept, at least, the options as shown with their default in `values.yaml`:
* https://github.com/rancher/fleet/blob/master/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-agent/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-agent/values.yaml
## Environment Variables
@ -16,13 +16,13 @@ The controllers can be started with these environment variables:
* `CATTLE_DEV_MODE` - used to debug wrangler, not usable
* `FLEET_CLUSTER_ENQUEUE_DELAY` - tune how often non-ready clusters are checked
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/master/docs/performance.md)
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/main/docs/performance.md)
## Configuration
In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.
The config [struct](https://github.com/rancher/fleet/blob/master/pkg/config/config.go#L40-L52) is used in both config maps:
The config [struct](https://github.com/rancher/fleet/blob/main/pkg/config/config.go#L40-L52) is used in both config maps:
* cattle-fleet-system/fleet-agent
* cattle-fleet-system/fleet-controller

10
versioned_docs/version-0.8/ref-configuration.md
View File

@ -6,9 +6,9 @@ A reference list of, mostly internal, configuration options.
The Helm charts accept, at least, the options as shown with their default in `values.yaml`:
* https://github.com/rancher/fleet/blob/master/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-agent/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-agent/values.yaml
## Environment Variables
@ -16,13 +16,13 @@ The controllers can be started with these environment variables:
* `CATTLE_DEV_MODE` - used to debug wrangler, not usable
* `FLEET_CLUSTER_ENQUEUE_DELAY` - tune how often non-ready clusters are checked
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/master/docs/performance.md)
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/main/docs/performance.md)
## Configuration
In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.
The config [struct](https://github.com/rancher/fleet/blob/master/pkg/config/config.go#L40-L52) is used in both config maps:
The config [struct](https://github.com/rancher/fleet/blob/main/pkg/config/config.go#L40-L52) is used in both config maps:
* cattle-fleet-system/fleet-agent
* cattle-fleet-system/fleet-controller

10
versioned_docs/version-0.9/ref-configuration.md
View File

@ -6,9 +6,9 @@ A reference list of, mostly internal, configuration options.
The Helm charts accept, at least, the options as shown with their default in `values.yaml`:
* https://github.com/rancher/fleet/blob/master/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/master/charts/fleet-agent/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-crds/values.yaml
* https://github.com/rancher/fleet/blob/main/charts/fleet-agent/values.yaml
## Environment Variables
@ -16,13 +16,13 @@ The controllers can be started with these environment variables:
* `CATTLE_DEV_MODE` - used to debug wrangler, not usable
* `FLEET_CLUSTER_ENQUEUE_DELAY` - tune how often non-ready clusters are checked
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/master/docs/performance.md)
* `FLEET_CPU_PPROF_PERIOD` - used to turn on [performance profiling](https://github.com/rancher/fleet/blob/main/docs/performance.md)
## Configuration
In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.
The config [struct](https://github.com/rancher/fleet/blob/master/pkg/config/config.go#L40-L52) is used in both config maps:
The config [struct](https://github.com/rancher/fleet/blob/main/pkg/config/config.go#L40-L52) is used in both config maps:
* cattle-fleet-system/fleet-agent
* cattle-fleet-system/fleet-controller