You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@camel.apache.org by "Andrea Cosentino (Jira)" <ji...@apache.org> on 2023/12/05 08:29:00 UTC

[jira] [Assigned] (CAMEL-20185) Kubernetes CronJob Component

     [ https://issues.apache.org/jira/browse/CAMEL-20185?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino reassigned CAMEL-20185:
----------------------------------------

    Assignee: Andrea Cosentino

> Kubernetes CronJob Component
> ----------------------------
>
>                 Key: CAMEL-20185
>                 URL: https://issues.apache.org/jira/browse/CAMEL-20185
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-kubernetes
>            Reporter: Matthias Bechtold
>            Assignee: Andrea Cosentino
>            Priority: Major
>
> We are building an end to end test with Camel and want to read the {{.jobTemplate.spec}} field from a k8s {{{}CronJob{}}}.
> Since there is (apparently) no {{CronJob}} component like there is ["kubernetes-job"|https://camel.apache.org/components/next/kubernetes-job-component.html], we ended up building it the hard way using fabric8's k8s client.
> What we have done so far, could be greatly simplified by having a "kubernetes-cronjob" Camel component, with an operation "getCronJob", which would retrieve the {{CronJob}} manifest from k8s and put it into a message header or body.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)