<commit_before>---
kep-number: 27
title: Resource Quota based on Node Labels
authors:
  - "@vishh"
  - "@bsalamat"
owning-sig: sig-scheduling
participating-sigs:
reviewers:
  - "@derekwaynecarr"
  - "@davidopp"
approvers:
  - TBD
editor: TBD
creation-date: 2018-08-23
status: provisional
---

# Resource Quota based on Node Labels

## Summary

Allowing Resource Quota to be applied on pods based on their node selector configuration opens up a flexible interface for addressing some immediate and potential future use cases.

## Motivation

As a kubernetes cluster administrator, I'd like to,

1. Restrict namespaces to specific HW types they can consume. Nodes are expected to be homogeneous wrt. to specific types of HW and HW type will be exposed as node labels.
   * A concrete example - An intern should only use the cheapest GPU available in my cluster, while researchers can consume the latest or most expensive GPUs.
2. Restrict compute resources consumed by namespaces on different zones or dedicated node pools.
3. Restrict compute resources consumed by namespaces based on policy (FIPS, HIPAA, etc) compliance on individual nodes.
<commit_msg>Add sig-architecture as a participating sig<commit_after>---
kep-number: 27
title: Resource Quota based on Node Labels
authors:
  - "@vishh"
  - "@bsalamat"
owning-sig: sig-scheduling
participating-sigs: sig-architecture
reviewers:
  - "@derekwaynecarr"
  - "@davidopp"
approvers:
  - TBD
editor: TBD
creation-date: 2018-08-23
status: provisional
---

# Resource Quota based on Node Labels

## Summary

Allowing Resource Quota to be applied on pods based on their node selector configuration opens up a flexible interface for addressing some immediate and potential future use cases.

## Motivation

As a kubernetes cluster administrator, I'd like to,

1. Restrict namespaces to specific HW types they can consume. Nodes are expected to be homogeneous wrt. to specific types of HW and HW type will be exposed as node labels.
   * A concrete example - An intern should only use the cheapest GPU available in my cluster, while researchers can consume the latest or most expensive GPUs.
2. Restrict compute resources consumed by namespaces on different zones or dedicated node pools.
3. Restrict compute resources consumed by namespaces based on policy (FIPS, HIPAA, etc) compliance on individual nodes.

{'fraction_non_alphanumeric': 0.05859872611464968, 'fraction_numerical': 0.011040339702760084, 'mean_word_length': 4.318284424379232, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6633306', 'n_tokens_mistral': 675, 'n_tokens_neox': 618, 'n_words': 322}