when cluster is not available should build not fail when deploy requested ?

[maxandersen]

Describe the bug
have cluster configured in kube but the cluster being down/not reachable:
run mvn clean package -Dquarkus.kubernetes.deploy=true

and you get output like this:

[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[ERROR] [io.quarkus.kubernetes.deployment.KubernetesDeploy] Although a Kubernetes deployment was requested, it will however not take place because there was an error during communication with the API Server: An error has occurred.
[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[INFO] [org.jboss.threads] JBoss Threads version 3.1.1.Final
[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[WARNING] Error reading service account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token]. Ignoring.
[INFO] [io.quarkus.deployment.pkg.steps.JarResultBuildStep] Building thin jar: /Users/max/Dropbox/code/openshift-deployment/target/simple-1.0.0-SNAPSHOT-runner.jar
[INFO] Initializing dekorate session.
[INFO] Default s2i build generator....
[INFO] Generating manifests.
[INFO] Processing kubernetes configuration.
[INFO] Processing openshift configuration.
[INFO] Processing s2i configuration.
[INFO] Closing dekorate session.
[INFO] [io.quarkus.deployment.QuarkusAugmentor] Quarkus augmentation completed in 8761ms
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

Expected behavior
I would have expected a BUILD FAILURE here.

Actual behavior
build marked as success despite there are errors.

[maxandersen]

in addition at no point do we actually print out which server/cluster/api endpoint that is being pushed to - hard to debug.

[geoand]

Makes sense - I'll take care of it.