Linkerd CLI, The Control Plane Rendered With No Cluster

linkerd (edge channel) on EL 10 from the GitHub release, pinned by a SHA-256 the role carries (the vendor publishes no checksum file), re-checked by the live test, which then has install --ignore-cluster render the control plane (at least three Deployments expected) and check --pre stop at the missing cluster. Pinned. Original role, live-tested on Rocky Linux 10.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

ansibleMulti-cloud & platform-agnosticKubernetesv1.0.0live-tested

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

Argo CD CLI, Checked Against The Published Checksums Argo Workflows CLI, A Workflow Linted Offline, One Refused Cilium CLI, Checked Against The Published Checksums Flux CLI, Checked Against The Published Checksums Helm, Checked Against The Published Hash Helmfile, Checked Against The Published Checksums KubeLinter, Four Findings On A Bare Deployment Kyverno CLI, A Policy Applied Both Ways

The same job on other clouds

This module has no cross-cloud peer set in the catalogue, so there is no portability comparison to draw.

Installing it

module "ansible_linkerd" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-linkerd/any"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.