-
Notifications
You must be signed in to change notification settings - Fork 523
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for CronJob controller resources #1954
Comments
Just like JobHandler, we need to implement CronJobHandler as well. How should the schedule be provided? |
I thought there was already an issue for tracking this |
This is one of the improvements that should be completed to simplify the configuration of projects such as: https://github.com/ammbra/cat-adoption-batch |
@rohanKanojia I tried to add support for cronjob but was not able to provide schedule can you take a look? |
@anurag-rajawat : I can see you provided |
I'm sorry for not being clear, I want to know how can we provide schedule in |
When I run $ mvn k8s:resource -Djkube.enricher.jkube-controller.type=cronjob or add configuration in pom file like <configuration>
<enricher>
<config>
<jkube-controller>
<type>CronJob</type>
<schedule>"* * * * *"</schedule>
</jkube-controller>
</config>
</enricher>
</configuration> I get Failed to execute goal org.eclipse.jkube:kubernetes-maven-plugin:1.11-SNAPSHOT:resource (default-cli) on project random-generator: Execution default-cli of goal org.eclipse.jkube:kubernetes-maven-plugin:1.11-SNAPSHOT:resource failed: No schedule is specified! So how to pass cronjob specs? |
I think you have defined expectation for schedule to be like this: <configuration>
<resources>
<schedule>"* * * * *"</schedule
</resources>
</configuration> |
In order to define it in enricher configuration, you need to add it here: |
Thank you! |
Where should we define expectations for the And do we need to validate the corn schedule expression or leave it to Kubernetes? |
Hi there, Maybe this https://github.com/eclipse/jkube/tree/master/quickstarts/maven/hello-world is good enough edit: ok I have not seen that one https://github.com/ammbra/cat-adoption-batch |
In my opinion, we should leave it to Kubernetes. |
For this first iteration we can define all of the configuration params in the Enricher configuration. We can later on move some of them to the resource configuration if it makes sense. There are still some changes (I think yet to be merged) to refactor the resource configuration class in order to have a more structured and organized configuration. |
How to do that without defining those params in resource configuration class? If we don't define those params in resource configuration then how can we add them in cronjob specs? |
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Signed-off-by: Anurag Rajawat <[email protected]>
Hi like job in jkube, we can create directly job, such thing is not available for cron job. can you please create for cronjob like job. there should be jkube.enricher.jkube-controller.type for cronjob too
The text was updated successfully, but these errors were encountered: