There are two different agent resources deployed on Rancher managed clusters:
For a conceptual overview of how the Rancher server provisions clusters and communicates with them, refer to the architecture.
cattle-cluster-agent is used to connect to the Kubernetes API of Rancher Launched Kubernetes clusters. The
cattle-cluster-agent is deployed using a Deployment resource.
cattle-node-agent is used to interact with nodes in a Rancher Launched Kubernetes cluster when performing cluster operations. Examples of cluster operations are upgrading Kubernetes version and creating/restoring etcd snapshots. The
cattle-node-agent is deployed using a DaemonSet resource to make sure it runs on every node. The
cattle-node-agent is used as fallback option to connect to the Kubernetes API of Rancher Launched Kubernetes clusters when
cattle-cluster-agent is unavailable.
cattle-cluster-agent uses either a fixed set of tolerations, or dynamically-added tolerations based on taints applied to the control plane nodes. This structure allows Taint based Evictions to work properly for
If control plane nodes are present in the cluster, the default tolerations will be replaced with tolerations matching the taints on the control plane nodes. The default set of tolerations are described below.
|Note: These are the default tolerations, and will be replaced by tolerations matching taints applied to controlplane nodes.
cattle-cluster-agent Deployment has preferred scheduling rules using
preferredDuringSchedulingIgnoredDuringExecution, favoring to be scheduled on nodes with the
controlplane node. When there are no controlplane nodes visible in the cluster (this is usually the case when using Clusters from Hosted Kubernetes Providers), you can add the label
cattle.io/cluster-agent=true on a node to prefer scheduling the
cattle-cluster-agent pod to that node.
See Kubernetes: Assigning Pods to Nodes to find more information about scheduling rules.
preferredDuringSchedulingIgnoredDuringExecution configuration is shown in the table below: