jkube: Config Map Enricher appears to be loosing quotes and then corrupting data
Describe the bug
Hi, I have an example where we have a configmap template with data like this
data:
report_date: "2020-01-01"
After the resource action the kubernetes yml has this
data:
report_date: 2020-01-01
which then results in a right mess in the deployed CM with the response json showing this
"report_date" : "1577836800000"
I cant for the life of me understand why the quotes would be dropped but I am hoping its something easy to rectify
Eclipse JKube version
1.8.0
Component
Kubernetes Maven Plugin
Apache Maven version
3.8.3
Gradle version
No response
Steps to reproduce
1: create a configmap template with the following
data:
report_date: "2020-01-01"
run mvn k8s:resource the resultant hydrated manifest will be
data:
report_date: 2020-01-01
Expected behavior
should be
data:
report_date: "2020-01-01"
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
other (please specify in additional context)
Environment
Linux
Eclipse JKube Logs
No response
Sample Reproducer Project
No response
Additional context
kubernetes 1.19
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 18 (12 by maintainers)
Commits related to this issue
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to rohanKanojia/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to rohanKanojia/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to rohanKanojia/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to fabric8io/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to fabric8io/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to fabric8io/kubernetes-client by rohanKanojia 2 years ago
- fix (kubernetes-client-api) : Configure SnakeYaml to ignore converting timestamps to Date objects Related to https://github.com/eclipse/jkube/issues/1647 + Add custom Resolver for SnakeYaml which wi... — committed to fabric8io/kubernetes-client by rohanKanojia 2 years ago
certainly, I will get on that today and get back to you.
it it looking good thanks, the date looks to be as expected when delivered into the cluster. I have also uplifted the istio-api to use the fabric8 version and that looks all good thanks
We’ve bumped the Kubernetes Client dependency to 6.1.1 in this release. The older Istio Client (the one you are using) won’t be compatible with the new Kubernetes Client version. Make sure to migrate to use the new extensions that’s available along with the client (the one Rohan linked).
I don’t think istio client dependency comes from jkube.
Istio Client is now available via Fabric8 https://search.maven.org/artifact/io.fabric8/istio-client/6.1.1/jar