Envoy On Loopback, Its Admin Interface Kept Off The Network

Envoy from the upstream release, SHA-256 pinned, with its listener and its admin interface on loopback and its bootstrap checked by the installed release before it lands. The live test proxies a request to an upstream it serves, stops the upstream and sees Envoy answer 503 itself, and reads both outcomes in the admin stats. 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-agnosticLoad Balancingv1.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.

HAProxy That Refuses TLS 1.0 keepalived, An Address That Moves, And Is Watched Moving

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

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