Description

Failure to run peer pods on Azure with a custom OSC operator (current HEAD of devel).

Steps to reproduce

1. Deployed self-managed cluster on Azure (and configured everything to do peer pods)
2. Deployed locally built operator from branch devel
3. Populated peer pods CM using in repo script ./scripts/cm-helpers/pp-cm-helper.sh
4. Created KataConfig with peer pods enabled
5. Wait for installation to succeed (and image created in Azure)
6. Start a simple peer pod

Expected result

Peer pods starts and eventually reaches the Running state

Actual result

Peer pod stays at ContainerCreating state and CAA has the following errors :

2025/09/08 11:16:47 [adaptor/proxy] Retrying failed agent proxy connection: dial tcp 10.0.128.7:15150: connect: connection refused
2025/09/08 11:16:48 [adaptor/proxy] Retrying failed agent proxy connection: dial tcp 10.0.128.7:15150: connect: connection refused
2025/09/08 11:16:48 [adaptor/proxy] Retrying failed agent proxy connection: dial tcp 10.0.128.7:15150: connect: connection refused
...

Impact

GA peer pods feature is broken

Env

Azure (self-managed)
OCP 4.19.9
OSC from devel (032aefcc6fb33d4a1e261b0b00fa2870034b9970)

Additional helpful info

Downstream CAA doesn't work with the Azure community images 0.14.0 and 0.15.0.