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 cronjobs #1562

Closed
luispabon opened this Issue Jan 10, 2017 · 14 comments

Comments

Projects
None yet
7 participants
@luispabon
Copy link

luispabon commented Jan 10, 2017

Would be great if Dashboard would support cronjobs in the same way it supports jobs (cronjobs being a level above jobs).

@ianlewis

This comment has been minimized.

Copy link
Contributor

ianlewis commented Jan 13, 2017

We probably want cronjobs to go at least beta before implementing this.

@libnux

This comment has been minimized.

Copy link

libnux commented Mar 13, 2017

It seems that Cronjobs will go beta in 1.6 release according to the following issue in 1.6 milestone:

kubernetes/kubernetes#41039

@floreks

This comment has been minimized.

Copy link
Member

floreks commented Mar 13, 2017

@luispabon Good idea. We'll look into that after the release.

@libnux

This comment has been minimized.

Copy link

libnux commented Mar 15, 2017

Unfortunately , cronjobs' going beta postponed to v1.7.

@silverkorn

This comment has been minimized.

Copy link

silverkorn commented Jul 19, 2017

Greetings!
Any updates?

@oscarbatori

This comment has been minimized.

Copy link

oscarbatori commented Jul 25, 2017

Is there an open PR for this, or is there design work required to figure out where this sits in the Dashboard UI? CronJob doesn't seem to fit neatly into any of the existing tabs.

@maciaszczykm

This comment has been minimized.

Copy link
Member

maciaszczykm commented Jul 25, 2017

@oscarbatori We can always introduce new tab, but you are right. We need to discuss it a bit before implementing it.

@oscarbatori

This comment has been minimized.

Copy link

oscarbatori commented Jul 25, 2017

@maciaszczykm is this the appropriate forum for discussing features, or is JIRA/mailing-list used for that?

I think cronjobs just below pods would probably do the trick. I think probably critical information to replicate kubectl get functionality:

  1. schedule
  2. name
  3. suspend
  4. active

Also, we might want to look at separating cronjob pods from longer running pods. As an example, it's pretty easy to see how a litany of cronjobs could end up polluting the pod list with the status of transient pods:
screen shot 2017-07-25 at 9 53 07 am

Happy to help, though I'd be a first time contributer.

@maciaszczykm

This comment has been minimized.

Copy link
Member

maciaszczykm commented Jul 25, 2017

@maciaszczykm is this the appropriate forum for discussing features, or is JIRA/mailing-list used for that?

@oscarbatori It is a good place.

I will take a look on your proposal later.

@oscarbatori

This comment has been minimized.

Copy link

oscarbatori commented Jul 25, 2017

@maciaszczykm thanks! Feel free to reach out if you want some help!

@maciaszczykm

This comment has been minimized.

Copy link
Member

maciaszczykm commented Aug 4, 2017

@oscarbatori We have updated our Kubernetes deps to 1.7.2 so it is a good time to start working on it. Are you willing to do so? We can guide you if you want. Just start with the backend and take Replica Sets as an example. Cron Jobs have to be in Workloads menu which we keep sorted alphabetically.

@oscarbatori

This comment has been minimized.

Copy link

oscarbatori commented Aug 4, 2017

@maciaszczykm yes, I can take a look this weekend!

Do you use Gitter? Just in case questions come up.

@floreks

This comment has been minimized.

Copy link
Member

floreks commented Aug 4, 2017

You can find us on: https://kubernetes.slack.com SIG-UI

@oscarbatori

This comment has been minimized.

Copy link

oscarbatori commented Aug 4, 2017

Swell, thanks guys!

@maciaszczykm maciaszczykm added this to the 1.8 milestone Oct 24, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment