davsclaus opened a new pull request, #30034: URL: https://github.com/apache/camel/pull/30034
JIRA: [CAMEL-26934](https://issues.apache.org/jira/browse/CAMEL-26934), item 6 (cronjob bullet) and item 7 (delete and CronJobs). - **`camel kubernetes delete`** deleted the Deployment, Service, ConfigMaps, Secrets, Ingress and Knative Service of an integration, but never its CronJob. It now deletes the CronJob too, which cascades to its jobs and pods. Like the Ingress and the Knative Service, a cluster without that API does not fail the delete. - **`cronjob.backoffLimit=0`** (no retry of a failed job) was left out (`> 0`), so Kubernetes used its default of 6 retries. 0 is now kept. - **`cronjob.enabled=true` without `cronjob.schedule`** generated no workload at all (no CronJob, and no Deployment either) and exited with 0. It now exits with 2: `cronjob.enabled=true needs cronjob.schedule, such as cronjob.schedule=0 * * * *`. Tests: `KubernetesDeleteTest.shouldDeleteTheCronJob` (fails on main), `KubernetesExportTest.aBackoffLimitOfZeroIsKept` and `aCronjobWithoutScheduleIsAUsageError`. Kubernetes plugin suite: 168 tests, green. Not changed: `delete` still exits with 0 when nothing is found. The mock-server tests answer each delete with an empty body, which looks the same, so that change needs its tests rewritten first. _Claude Code on behalf of davsclaus_ 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
