Open metalpalo opened 2 years ago
The team was thinking about providing more visibility into any cronjob that is using a version which is older than the current default. This would enable you to decide when it is appropriate to recreate the cron job. We have added this to the general backlog as a feature request. I don't think that using init-container
for this purpose is aligned with the use-case of init-containers generally in k8s.
Used environment scdf 2.9.2 release.
Task application exporter was registered with two versions like: docker:exporter:0.0.1.BUILD-SNAPSHOT (DEFAULT) docker:exporter:0.0.2.BUILD-SNAPSHOT
Then application was successfully scheduled and kubernetes cronjob created with image 0.0.1.BUILD-SNAPSHOT
We switched to version 0.0.2.BUILD-SNAPSHOT as default via Application->Manage Version
After this, does exist some way to automatically reschedule kubernetes cronjob?
For this moment I had to delete existing one and create new one.
Another question: Does exist some way to create two scheduler with both versions? I've tried to put something like this but it doesnt work: deployer.exporter.kubernetes.init-container.image-name=exporter:0.0.2.BUILD-SNAPSHOT