kubeseal, A Secret Sealed Offline

kubeseal on EL 10 from the GitHub release, refused by Ansible's get_url unless its SHA-256 is the one in the project's checksums file, and re-checked with sha256sum -c by the live test, which then generates a throwaway certificate, seals a one-key Secret against it with no cluster and expects a SealedSecret document. The controller stays per cluster. 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 Velero CLI, Checked Against The Published Checksums istioctl, Checked, And Not Waiting For A Cluster k9s, Checked Against The Published Checksums

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

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