Configuration

A reference list of, mostly internal, configuration options.

Helm Charts

The Helm charts accept, at least, the options as shown with their default in values.yaml:

Environment Variables

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

Configuration

In cluster configuration for the agent and fleet manager. Changing these can lead to full re-deployments.

The config struct is used in both config maps:

  • cattle-fleet-system/fleet-agent

  • cattle-fleet-system/fleet-controller

Labels

Labels used by fleet:

  • fleet.cattle.io/agent=true - NodeSelector label for agent’s deployment affinity setting

  • fleet.cattle.io/non-managed-agent - managed agent bundle won’t target Clusters with this label

  • fleet.cattle.io/repo-name - used on Bundle to reference the git repo resource

  • fleet.cattle.io/bundle-namespace - used on BundleDeployment to reference the Bundle resource

  • fleet.cattle.io/bundle-name - used on BundleDeployment to reference the Bundle resource

  • fleet.cattle.io/managed=true - cluster namespaces with this label will be cleaned up. Other resources will be cleaned up if it is in a label. Used in Rancher to identify fleet namespaces.

  • fleet.cattle.io/bootstrap-token - unused

Annotations

Annotations used by fleet:

  • fleet.cattle.io/agent-namespace

  • fleet.cattle.io/bundle-id

  • fleet.cattle.io/cluster, fleet.cattle.io/cluster-namespace - used on a cluster namespace to reference the cluster registration namespace and cluster name

  • fleet.cattle.io/cluster-group

  • fleet.cattle.io/cluster-registration-namespace

  • fleet.cattle.io/cluster-registration

  • fleet.cattle.io/commit

  • fleet.cattle.io/managed - appears unused

  • fleet.cattle.io/service-account

SUSE® Rancher Prime Continuous Delivery agent configuration

Tolerations, affinity and resources can be customized for the SUSE® Rancher Prime Continuous Delivery agent. These fields can be provided when creating a Cluster, see Registering Downstream Cluster for more info on how to create Clusters. Default configuration will be used if these fields are not provided.

If you change the resources limits, make sure the limits allow the fleet-agent to work normally.

Keep in mind that if you downgrade SUSE® Rancher Prime Continuous Delivery to a previous version than v0.7.0 SUSE® Rancher Prime Continuous Delivery will fallback to the built-in defaults. Agents will redeploy if they had custom affinity. If SUSE® Rancher Prime Continuous Delivery version number does not change, redeployment might not be immediate.