Federated Jobs feature

[dhilipkumars]

Feature Description

• One-line feature description (can be used as a release note):
• Primary contact (assignee): @quinton-hoole
• Responsible SIGs: @kubernetes/sig-federation-feature-requests
• Design proposal link (community repo): https://docs.google.com/document/d/1TZ4ZMZ8AEOlVyK6H_q-zNpAdlzTip8sxMQUVQeQ-O-w/edit#heading=h.v3yscf7s8679
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @quinton-hoole @madhusudancs @irfanurrehman
• Approver (likely from SIG/area to which feature belongs): @quinton-hoole
• Feature target (which target equals to which milestone):
  • Alpha release target (1.7): Inital implementation of the design along with API.

[davidopp]

Is there anything here that's specific to batch jobs? It seems like the goals you described would also make sense for long-running services.

BTW we have a proposal that introduces the concept of batch queues. Assuming that the proposal is adopted in some form, it might make sense to think of a federated/global queue that makes the placement decision when it decides to "admit" a job.

[dhilipkumars]

I think the better person to answer would be @quinton-hoole and @jianhuiz

[ghost]

@davidopp The intention of this feature is to support precisely the Kubernetes Jobs API to start with . i.e. https://kubernetes.io/docs/concepts/workloads/controllers/jobs-run-to-completion/

We should definitely extend it over time to support other types of workloads, as they become supported by Kubernetes. I will take a look at your batch queues design proposal - it looks interesting.

[ghost]

Assigning this to myself as a proxy for @jianhuiz whom I cannot seem to assign to.

[davidopp]

I just meant that since the primary functionality described here is picking a cluster or clusters, extending it to handle something like ReplicaSet (or even StatefulSet) might be pretty straightforward. The description didn't sound very Job-specific.

[idvoretskyi]

@quinton-hoole I've updated the feature description to fit the new template. Please, fill the empty fields in the new template (their actual state was unclear).

[kevin-wangzefeng]

xref kubernetes/kubernetes#34261

[idvoretskyi]

@quinton-hoole milestone has been updated to 1.8. Which stage will this feature target for 1.8?

[ghost]

@idvoretskyi alpha as per label.

[idvoretskyi]

@quinton-hoole @kubernetes/sig-federation-feature-requests any updates for 1.8? Is this feature still on track for the release?

[jianhuiz]

It's in 1.8 as alpha feature without re-balancing implemented
kubernetes/kubernetes#45187

kubernetes/kubernetes#36197
kubernetes/website#5485

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

[ghost]

/lifecycle frozen

[justaugustus]

@quinton-hoole Any plans for this in 1.11?

If so, can you please ensure the feature is up-to-date with the appropriate:

• Description
• Milestone
• Assignee(s)
• Labels:
  • stage/{alpha,beta,stable}
  • sig/*
  • kind/feature

cc @idvoretskyi

[irfanurrehman]

@justaugustus, I would suggest closing this issue here, as federation features are no longer released with k8s releases.

[justaugustus]

Thanks for the update, @irfanurrehman!
/close