chore: kind processor always loads imgs on deploy

quarkusio · Feb 6, 2023 · 8b233bc · 8b233bc
1 parent afe4a37
commit 8b233bc
Showing 1 changed file with 4 additions and 6 deletions.
diff --git a/...ns/kubernetes/kind/deployment/src/main/java/io/quarkus/kind/deployment/KindProcessor.java b/...ns/kubernetes/kind/deployment/src/main/java/io/quarkus/kind/deployment/KindProcessor.java
@@ -120,11 +120,9 @@ public List<DecoratorBuildItem> createDecorators(ApplicationInfoBuildItem applic
     @BuildStep
     public void postBuild(ContainerImageInfoBuildItem image, List<ContainerImageBuilderBuildItem> builders,
             @SuppressWarnings("unused") BuildProducer<ArtifactResultBuildItem> artifactResults) {
-        boolean isLoadSupported = builders.stream().anyMatch(b -> b.getBuilder().equals("docker")
-                || b.getBuilder().equals("jib")
-                || b.getBuilder().equals("buildpack"));
-        if (isLoadSupported) {
-            ExecUtil.exec("kind", "load", "docker-image", image.getImage());
-        }
+        //We used to only perform the action below when using known builders that play nicely with kind (e.g. docker)
+        //However, this excluded users that are just using external tools for building including the cli (e.g. quarkus image build docker).
+        //So, we now always perform this step
+        ExecUtil.exec("kind", "load", "docker-image", image.getImage());
     }
 }