Where Does Linkerd Store Mesh Configs?
Where Linkerd keeps configs in cluster on Linux servers. Full paths are listed below. More below. See below.
Last updated
Linkerd is ultralight mesh with cluster storage. Your link definitions, policies, and telemetry live in etcd through the API server. Nodes run linkerd2 proxies with local cache.
Same etcd plus control plane means same mesh. Exact CRD versions shift with edge versus stable releases. Keep YAML exports beside snapshots. One missing revision restores routes without history. For moves, freeze changes first to avoid split config during copies. Check the in app storage readout when sizes look wrong on different releases.
Where Linkerd Mesh stores this, by platform
/var/lib/linkerd (proxy cache, configs in etcd)
Mesh configs live in cluster etcd with revisions attached. Back up etcd plus control plane files. Match releases before restore. Proxies cache locally.
Frequently asked questions
How do I migrate Linkerd to a new cluster?
Back up etcd snapshots plus Linkerd control plane configs with services steady, then install the same release on the new cluster before restore. Mesh configs follow etcd. Mixed releases can refuse old CRDs, so match versions first.
Does Linkerd back up mesh configs?
Yes, in cluster etcd per namespace with revision history attached. Nodes hold a working copy plus proxy cache. Views rebuild after restore. Export YAMLs from namespaces for records, since node files alone are runtime state.
Notice an outdated path? Let us know.