dhi.io/linkerd-controller
Linkerd Controller
The Linkerd control plane controller, with its destination, identity, proxy injector and policy controller.
pushed 10 hours ago
linux/amd64, linux/arm64
26.48 MB
for linux/amd64
329
for linux/amd64
Active support
linkerd2-controller, linkerd-policy-controller
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
-
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About Linkerd Controller
Linkerd is a CNCF service mesh for Kubernetes. The Linkerd controller image runs the control plane
components that configure the mesh: destination serves service discovery and routing information to the proxies,
identity issues their mutual TLS certificates, proxy-injector adds the proxy to pods, sp-validator validates
service profiles, heartbeat reports anonymous version checks, and service-mirror mirrors services between clusters
for the Linkerd multicluster extension. The same image carries the policy controller that serves inbound authorization
policy to the proxies and keeps the policy resource status up to date.
This image is the controller container the Linkerd Helm chart runs for the linkerd-destination, linkerd-identity
and linkerd-proxy-injector deployments and for the linkerd-heartbeat job.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
Linkerd® is a registered trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.
Kubernetes® is a trademark of the Linux Foundation. All rights in the mark are reserved to the Linux Foundation. Any use by Docker is for referential purposes only and does not indicate sponsorship, endorsement, or affiliation.