summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJiangtian Li <jiangtianli@hotmail.com>2018-01-30 09:42:26 -0800
committerJiangtian Li <jiangtianli@hotmail.com>2018-01-30 09:42:26 -0800
commit6d08a8213318d63d8ab49fe326afdb6b49037e33 (patch)
tree6342336b742d390bcab6922393f8a8e06fbde2be
parent2421112c60c1f6acb188c72371ed2ab780322942 (diff)
Add feature request link
-rw-r--r--contributors/design-proposals/node/cri-windows.md3
1 files changed, 3 insertions, 0 deletions
diff --git a/contributors/design-proposals/node/cri-windows.md b/contributors/design-proposals/node/cri-windows.md
index 711f9659..9793b2f8 100644
--- a/contributors/design-proposals/node/cri-windows.md
+++ b/contributors/design-proposals/node/cri-windows.md
@@ -16,6 +16,9 @@ On the Windows platform, processes may be assigned to a job object, which can ha
## Umbrella Issue
[#56734](https://github.com/kubernetes/kubernetes/issues/56734)
+## Feature Request
+[#547](https://github.com/kubernetes/features/issues/547)
+
## Motivation
The goal is to start filling the gap of platform support in CRI, specifically for Windows platform. For example, currrently in dockershim Windows containers are scheduled using the default resource constraints and does not respect the resource requests and limits specified in POD. With this proposal, Windows containers will be able to leverage POD spec and CRI to allocate compute resource and respect restriction.