Context: The konnectivity image is the one piece of software that hypershift deploys to workers that is not part of a release image. It is required to enable konnectivity between the KAS and the nodes. This imposes the following requirements on it:

• We need to host it in a manifest-list enabled repo with support for multiple architectures so we can handle multi-arch clusters in hypershift
• It needs to be mirrored into a customer's registry whenever they want to run their cluster off-line (along with the rest of the release payload)

By moving the konnectivity image into the payload, we get the above for free. A customer would not to perform a separate mirroring operation just for this image, and it would get a multi-arch build and repo along with the rest of the release payload.