New Resource API Proposal

[jiayingz]

Feature Description

• One-line feature description (can be used as a release note): A new resource API model to support non-native compute resources with rich set of resource properties.
• Primary contact (assignee): @vikaschoudhary16 @jiayingz
• Responsible SIGs: @kubernetes/sig-node-feature-requests @kubernetes/sig-scheduling-feature-requests
• Design proposal link (community repo): KEP: New Resource API proposal community#2265
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @derekwaynecarr @dchen1107 @bsalamat @vishh @MaciekPytel
• Approver (likely from SIG/area to which feature belongs): @derekwaynecarr @dchen1107 @bsalamat @thockin
• Feature target (which target equals to which milestone):
  • Alpha release target (1.12)
  • Beta release target (TBD)
  • Stable release target (TBD)

[jiayingz]

/stage alpha

[justaugustus]

Added to the 1.12 tracking sheet.
/assign @vikaschoudhary16 @jiayingz

[vishh]

Is this feature already confirmed to go alpha in v1.12 or is v1.12 just an estimate for now?

[jiayingz]

It is an estimate target.

[derekwaynecarr]

i think the target is a design that meets the community need, i think an implementation is a stretch goal.

[MaciekPytel]

Can we add a reviewer from sig-autoscaling? This will have a large impact on cluster autoscaling.

[justaugustus]

@vikaschoudhary16 @jiayingz @derekwaynecarr -- checking in again... any plans for this in 1.12?

[justaugustus]

@vikaschoudhary16 @jiayingz @derekwaynecarr --
Any update on docs status for this feature? Are we still planning to land it for 1.12?
At this point, code freeze is upon us, and docs are due on 9/7 (2 days).
If we don't here anything back regarding this feature ASAP, we'll need to remove it from the milestone.

cc: @zparnold @jimangel @tfogo

[jiayingz]

Lets remove it from 1.12 milestone.

[justaugustus]

Thanks for the update!
/milestone clear

[kacole2]

Hi
This enhancement has been tracked before, so we'd like to check in and see if there are any plans for this to graduate stages in Kubernetes 1.13. This release is targeted to be more ‘stable’ and will have an aggressive timeline. Please only include this enhancement if there is a high level of confidence it will meet the following deadlines:
Docs (open placeholder PRs): 11/8
Code Slush: 11/9
Code Freeze Begins: 11/15
Docs Complete and Reviewed: 11/27

Please take a moment to update the milestones on your original post for future tracking and ping @kacole2 so it can be included in the 1.13 Enhancements Tracking Sheet

All PRs for features have relevant release notes included as well.

Thanks!

[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.

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.