New flow affect all peer pods supported cloud platforms: AWS and Azure.
Since Peer pods was released as tech preview for OCP 4.13 (which has RHEL 9.x same as 4.14 and 4.15)
We do not test on OCP 4.12 (RHEL 8.6), but only OCP 4.15.x

New flow require re-testing the case when AMI_ID was provided into the configmap.
Finally some regression testing should be done for:

• Replacing manually AMI in configmap (should take effect after caa-daemon restart)
• Deleting kataconfig (image set in configmap should be removed)
• Negative case (like wrong credentials) to test troubleshooting OSC deployment failure
• Negative - deleting AMI_ID from configmap and caa-daemon restart should not trigger a new creation job and should fail gracefully