Skaffold, A Config Upgraded Across Schema Versions Offline

skaffold on EL 10 from the GitHub release; get_url refuses it unless its SHA-256 is in the vendor's per-asset .sha256, and the live test re-checks it, then has skaffold fix upgrade a v2beta29 config to the current schema, turns metrics off and reads the config back; the update check is off in profile.d. 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 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 Pluto, A Deprecated apiVersion Found

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_skaffold" {
  source  = "www.iac-bazaar.com/iac-bazaar/ansible-skaffold/any"
  version = "1.0.0"
}

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