In Kafka Connect, when Kafka Connect Build is used, it might cause problems when .spec.image and spec.build.output.image are set to the same image. This is because the .spec.image is used as FROM in the Dockerfile in Kafka Connect Build and the spec.build.output.image is used as the target where the new image is pushed. That means that it can possibly just loop and extend the previous built image and that might cause issues such as in https://cloud-native.slack.com/archives/C018247K8T0/p1692121624494459

We should consider doing validation to ensure that these two are different. While it might not catch all situations (e.g. when image streams are used), we should be able to easily catch the situations when they are identical.

However, we should also consider if this wouldn't break working stuff for some users. The error in the thread above was solved by fixing the images. But it has a weird error. I wonder if the weird error is caused because of something run over and the FROM image is unusable anymore or needs too much memory to unpack etc. So there might be also users without any problems for which this validation will break it.

Created by Strimzi#8990