ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #rancher
Step‑by‑step guide to connect Rancher to an LDAP server for centralized authentication and role‑based access control.
Decide between Longhorn, Rook Ceph, and hostPath for dynamic storage in Rancher. Compare portability, scalability, and overhead, then see a step‑by‑step Longhorn install, PVC creation, node‑drain test, and snapshot restore.
Rancher Catalogs centralize Helm chart management by unifying repositories, auto‑syncing releases, and enforcing cluster‑level RBAC. This guide walks through adding a custom catalog, deploying an app, and choosing upgrade strategies.
Learn how to configure the Rancher Backup Operator to automate etcd snapshots to S3-compatible storage and recover cluster state during a disaster.
Goal: Determine whether to standardize on K3s for all downstream clusters managed by Rancher or to adopt a mixed approach that runs RKE2 in core/regulated workloads and K3s at the edge, while respecting limited CPU and memory budgets on branch hardware. Constraints: K3s delivers a small footprint with a single binary and SQLite datastore, fitting tightly con
Rancher Manager Cluster Agent Rancher utilizes a Cluster Agent deployed within managed clusters to maintain communication and state synchronization with the Rancher Manager. This mechanism ensures that configuration changes made in the centralized management plane are propagated to the downstream Kubernetes clusters. When a managed cluster experiences an ext
State Synchronization After Network Partitions Rancher relies on the cattle-cluster-agent to maintain a bidirectional communication channel with the management server. This integration ensures that configuration updates are pushed to downstream clusters and state changes are reported back to the manager. When a network partition occurs between the agent and
Rancher uses Cluster API to abstract infrastructure providers and manages node lifecycle through MachineDeployment objects. The Rancher UI reflects downstream cluster state via the cluster-agent and Rancher's internal resource cache. An unresolved behavior concerns the timing of node Ready status updates in the Rancher UI versus the actual Kubernetes API sta
Context Harvester v1.3–1.4 officially supports single-node clusters for development and edge scenarios. The installer provisions an embedded etcd member and sets the Longhorn default replica count to 1. For production HA, the documented path requires at least three server nodes, a 3-member etcd cluster, and a Longhorn default replica count of 3 with anti-aff
kubernetes
helm
k3s