Repository: quarkusio/quarkus
Issue: Kubernetes resources generation log not on par with what is generated

### Describe the bug

When you generate a container image and Kubernetes resources but not push the image to a remote Docker registry, the following logs is shown

```
[WARNING] [io.quarkus.kubernetes.deployment.KubernetesDeployer] A Kubernetes deployment was requested, but the container image to be built will not be pushed to any registry because "quarkus.container-image.registry" has not been set. The Kubernetes deployment will only work properly if the cluster is using the local Docker daemon. For that reason 'ImagePullPolicy' is being force-set to 'IfNotPresent'.
```

However, the generated resouce have `imagePullPolicy: Always`.

### Expected behavior

Either the log is updated either the generated resource is updated to match each other.

### Actual behavior

_No response_

### How to Reproduce?

_No response_

### Output of `uname -a` or `ver`

Ubuntu 22.04

### Output of `java -version`

17

### GraalVM version (if different from Java)

_No response_

### Quarkus version or git rev

2.14.0.Final

### Build tool (ie. output of `mvnw --version` or `gradlew --version`)

_No response_

### Additional information

_No response_

Changed files:
extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesDeployer.java

diff --git a/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesDeployer.java b/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesDeployer.java
index 3dcab91d48a..5a8dcbc4aa1 100644
--- a/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesDeployer.java
+++ b/extensions/kubernetes/vanilla/deployment/src/main/java/io/quarkus/kubernetes/deployment/KubernetesDeployer.java
@@ -41,7 +41,6 @@
 import io.quarkus.container.image.deployment.ContainerImageConfig;
 import io.quarkus.container.spi.ContainerImageInfoBuildItem;
 import io.quarkus.deployment.Capabilities;
-import io.quarkus.deployment.Capability;
 import io.quarkus.deployment.IsNormalNotRemoteDev;
 import io.quarkus.deployment.annotations.BuildProducer;
 import io.quarkus.deployment.annotations.BuildStep;
@@ -152,7 +151,6 @@ private DeploymentTargetEntry determineDeploymentTarget(
             ContainerImageConfig containerImageConfig) {
         final DeploymentTargetEntry selectedTarget;
 
-        boolean checkForMissingRegistry = true;
         boolean checkForNamespaceGroupAlignment = false;
         List<String> userSpecifiedDeploymentTargets = KubernetesConfigUtil.getExplictilyDeploymentTargets();
         if (userSpecifiedDeploymentTargets.isEmpty()) {
@@ -178,25 +176,10 @@ private DeploymentTargetEntry determineDeploymentTarget(
         }
 
         if (OPENSHIFT.equals(selectedTarget.getName())) {
-            checkForMissingRegistry = Capability.CONTAINER_IMAGE_S2I.equals(activeContainerImageCapability)
-                    || Capability.CONTAINER_IMAGE_OPENSHIFT.equals(activeContainerImageCapability);
-
             // We should ensure that we have image group and namespace alignment we are not using deployment triggers via DeploymentConfig.
             if (!targets.getEntriesSortedByPriority().get(0).getKind().equals("DeploymentConfig")) {
                 checkForNamespaceGroupAlignment = true;
             }
-
-        } else if (MINIKUBE.equals(selectedTarget.getName()) || KIND.equals(selectedTarget.getName())) {
-            checkForMissingRegistry = false;
-        } else if (containerImageConfig.isPushExplicitlyDisabled()) {
-            checkForMissingRegistry = false;
-        }
-
-        if (checkForMissingRegistry && !containerImageInfo.getRegistry().isPresent()) {
-            log.warn(
-                    "A Kubernetes deployment was requested, but the container image to be built will not be pushed to any registry"
-                            + " because \\"quarkus.container-image.registry\\" has not been set. The Kubernetes deployment will only work properly"
-                            + " if the cluster is using the local Docker daemon. For that reason 'ImagePullPolicy' is being force-set to 'IfNotPresent'.");
         }
 
         //This might also be applicable in other scenarios too (e.g. Knative on Openshift), so we might need to make it slightly more generic.