When you set the property quarkus.container-image.tag to a numberical value and then you generate a minikube.yml with the Minikube extension, the file cannot be applied by kubectl (while the JSON file works). Set letters instead of numbers, it works.
Expected behavior
When generating the manifest files with numbers, the minikube.json file can be applied by kubectl, so I expect the YAML file to be to (or both don't).
Actual behavior
Set the property quarkus.container-image.tag=123. Now generate the minikube.yml with a mvn package and the Minikube extension. When you execute the kubectl apply command you get:
$ kubectl apply -f target/kubernetes/minikube.yml
unable to decode "target/kubernetes/minikube.yml": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Labels: ReadString: expects " or n, but found 1, error found in #10 byte of ...|version":123},"name"|..., bigger context ...|:"code-with-quarkus","app.kubernetes.io/version":123},"name":"code-with-quarkus"}}|...
unable to decode "target/kubernetes/minikube.yml": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Labels: ReadString: expects " or n, but found 1, error found in #10 byte of ...|version":123},"name"|..., bigger context ...|:"code-with-quarkus","app.kubernetes.io/version":123},"name":"code-with-quarkus"},"spec":{"ports":[{|...
unable to decode "target/kubernetes/minikube.yml": resource.metadataOnlyObject.ObjectMeta: v1.ObjectMeta.Labels: ReadString: expects " or n, but found 1, error found in #10 byte of ...|version":123},"name"|..., bigger context ...|:"code-with-quarkus","app.kubernetes.io/version":123},"name":"code-with-quarkus"},"spec":{"replicas"|...
If you execute the same command but on the JSON file, it works:
$ kubectl apply -f target/kubernetes/minikube.json
serviceaccount/code-with-quarkus created
service/code-with-quarkus created
deployment.apps/code-with-quarkus created
Now, if you set the property to letters quarkus.container-image.tag=abc and regenerate the YAML manifest and apply it, it works (the JSON file too):
$ kubectl apply -f target/kubernetes/minikube.yml
serviceaccount/code-with-quarkus created
service/code-with-quarkus created
deployment.apps/code-with-quarkus created
To Reproduce
Steps to reproduce the behavior:
Generate a Quarkus application from scratch with the Minikube extension
Add the property quarkus.container-image.tag and set the value to 123
Generate the manifest files with mvn clean package
Execute kubectl apply -f target/kubernetes/kubernetes.yml it breaks
Configuration
quarkus.container-image.tag=123
Environment (please complete the following information):
Output of uname -a or ver: Darwin iMac-Pro-de-Antonio.local 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64
Output of java -version: java version "11.0.6" 2020-01-14 LTS
GraalVM version (if different from Java):
Quarkus version or git rev: 1.7.1.Final
Build tool (ie. output of mvnw --version or gradlew --version): Maven 3.6.3_1
Describe the bug
When you set the property
quarkus.container-image.tag
to a numberical value and then you generate aminikube.yml
with the Minikube extension, the file cannot be applied by kubectl (while the JSON file works). Set letters instead of numbers, it works.Expected behavior
When generating the manifest files with numbers, the
minikube.json
file can be applied by kubectl, so I expect the YAML file to be to (or both don't).Actual behavior
Set the property
quarkus.container-image.tag=123
. Now generate theminikube.yml
with amvn package
and the Minikube extension. When you execute thekubectl apply
command you get:If you execute the same command but on the JSON file, it works:
Now, if you set the property to letters
quarkus.container-image.tag=abc
and regenerate the YAML manifest and apply it, it works (the JSON file too):To Reproduce Steps to reproduce the behavior:
quarkus.container-image.tag
and set the value to123
mvn clean package
kubectl apply -f target/kubernetes/kubernetes.yml
it breaksConfiguration
Environment (please complete the following information):
uname -a
orver
: Darwin iMac-Pro-de-Antonio.local 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64 x86_64java -version
: java version "11.0.6" 2020-01-14 LTSmvnw --version
orgradlew --version
): Maven 3.6.3_1https://github.com/quarkusio/quarkus/issues/11823
$upstream:11823$