Skip to content

Commit 89d53a7

Browse files
hormeshormes
authored
Merge pull request #9 from eahydra/add_priority_class
add koordinator priroity classes
2 parents c016c01 + 670cc43 commit 89d53a7

File tree

6 files changed

+115
-3
lines changed

6 files changed

+115
-3
lines changed

‎versions/v0.1.0/README.md‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
# Koordinator v0.1.0
2+
3+
## Configuration
4+
5+
Note that installing this chart directly means it will use the default template values for Koordinator.
6+
7+
You may have to set your specific configurations if it is deployed into a production cluster, or you want to configure feature-gates.
8+
9+
### Optional: chart parameters
10+
11+
The following table lists the configurable parameters of the chart and their default values.
12+
13+
| Parameter | Description | Default |
14+
| ----------------------------------------- | ---------------------------------------------------------------- | ------------------------------- |
15+
| `featureGates` | Feature gates for Koordinator, empty string means all by default | ` ` |
16+
| `installation.namespace` | namespace for Koordinator installation | `koordinator-system` |
17+
| `installation.createNamespace` | Whether to create the installation.namespace | `true` |
18+
| `manager.log.level` | Log level that koord-manager printed | `4` |
19+
| `manager.replicas` | Replicas of koord-manager deployment | `2` |
20+
| `manager.image.repository` | Repository for koord-manager image | `koordinatorsh/koord-manager` |
21+
| `manager.image.tag` | Tag for koord-manager image | `v0.1.0` |
22+
| `manager.resources.limits.cpu` | CPU resource limit of koord-manager container | `1000m` |
23+
| `manager.resources.limits.memory` | Memory resource limit of koord-manager container | `1Gi` |
24+
| `manager.resources.requests.cpu` | CPU resource request of koord-manager container | `500m` |
25+
| `manager.resources.requests.memory` | Memory resource request of koord-manager container | `256Mi` |
26+
| `manager.metrics.port` | Port of metrics served | `8080` |
27+
| `manager.webhook.port` | Port of webhook served | `9443` |
28+
| `manager.nodeAffinity` | Node affinity policy for koord-manager pod | `{}` |
29+
| `manager.nodeSelector` | Node labels for koord-manager pod | `{}` |
30+
| `manager.tolerations` | Tolerations for koord-manager pod | `[]` |
31+
| `manager.resyncPeriod` | Resync period of informer koord-manager, defaults no resync | `0` |
32+
| `manager.hostNetwork` | Whether koord-manager pod should run with hostnetwork | `false` |
33+
| `scheduler.log.level` | Log level that koord-scheduler printed | `4` |
34+
| `scheduler.replicas` | Replicas of koord-scheduler deployment | `2` |
35+
| `scheduler.image.repository` | Repository for koord-scheduler image | `koordinatorsh/koord-scheduler` |
36+
| `scheduler.image.tag` | Tag for koord-scheduler image | `v0.1.0` |
37+
| `scheduler.resources.limits.cpu` | CPU resource limit of koord-scheduler container | `1000m` |
38+
| `scheduler.resources.limits.memory` | Memory resource limit of koord-scheduler container | `1Gi` |
39+
| `scheduler.resources.requests.cpu` | CPU resource request of koord-scheduler container | `500m` |
40+
| `scheduler.resources.requests.memory` | Memory resource request of koord-scheduler container | `256Mi` |
41+
| `scheduler.port` | Port of metrics served | `10251` |
42+
| `scheduler.nodeAffinity` | Node affinity policy for koord-scheduler pod | `{}` |
43+
| `scheduler.nodeSelector` | Node labels for koord-scheduler pod | `{}` |
44+
| `scheduler.tolerations` | Tolerations for koord-scheduler pod | `[]` |
45+
| `scheduler.hostNetwork` | Whether koord-scheduler pod should run with hostnetwork | `false` |
46+
| `koordlet.log.level` | Log level that koordlet printed | `4` |
47+
| `koordlet.image.repository` | Repository for koordlet image | `koordinatorsh/koordlet` |
48+
| `koordlet.image.tag` | Tag for koordlet image | `v0.1.0` |
49+
| `koordlet.resources.limits.cpu` | CPU resource limit of koordlet container | `500m` |
50+
| `koordlet.resources.limits.memory` | Memory resource limit of koordlet container | `256Mi` |
51+
| `koordlet.resources.requests.cpu` | CPU resource request of koordlet container | `0` |
52+
| `koordlet.resources.requests.memory` | Memory resource request of koordlet container | `0` |
53+
| `webhookConfiguration.failurePolicy.pods` | The failurePolicy for pods in mutating webhook configuration | `Ignore` |
54+
| `webhookConfiguration.timeoutSeconds` | The timeoutSeconds for all webhook configuration | `30` |
55+
| `crds.managed` | Koordinator will not install CRDs with chart if this is false | `true` |
56+
| `imagePullSecrets` | The list of image pull secrets for koordinator image | `false` |
57+
58+
Specify each parameter using the `--set key=value[,key=value]` argument to `helm install` or `helm upgrade`.
59+
60+
### Optional: feature-gate
61+
62+
Feature-gate controls some influential features in Koordinator:
63+
64+
| Name | Description | Default | Effect (if closed) |
65+
| ------------------------- | ---------------------------------------------------------------- | ------- | -------------------------------------- |
66+
| `PodMutatingWebhook` | Whether to open a mutating webhook for Pod **create** | `true` | Don't inject koordinator.sh/qosClass, koordinator.sh/priority and don't replace koordinator extend resources ad so on |
67+
| `PodValidatingWebhook` | Whether to open a validating webhook for Pod **create/update** | `true` | It is possible to create some Pods that do not conform to the Koordinator specification, causing some unpredictable problems |
68+
69+
70+
If you want to configure the feature-gate, just set the parameter when install or upgrade. Such as:
71+
72+
```bash
73+
$ helm install koordinator https://... --set featureGates="PodMutatingWebhook=true\,PodValidatingWebhook=true"
74+
```
75+
76+
If you want to enable all feature-gates, set the parameter as `featureGates=AllAlpha=true`.
77+
78+
### Optional: the local image for China
79+
80+
If you are in China and have problem to pull image from official DockerHub, you can use the registry hosted on Alibaba Cloud:
81+
82+
```bash
83+
$ helm install koordinator https://... --set manager.image.repository=koordinator-registry.cn-hangzhou.cr.aliyuncs.com/koordinator/koord-manager
84+
```

‎versions/v0.1.0/templates/koord-batch.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
apiVersion: scheduling.k8s.io/v1
2+
description: Offline tasks, computing tasks, etc.
3+
kind: PriorityClass
4+
metadata:
5+
name: koord-batch
6+
preemptionPolicy: PreemptLowerPriority
7+
value: 5000

‎versions/v0.1.0/templates/koord-free.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
apiVersion: scheduling.k8s.io/v1
2+
description: Run lowest-priority offline batch jobs, generally refers to not making resource budgets.
3+
kind: PriorityClass
4+
metadata:
5+
name: koord-free
6+
preemptionPolicy: PreemptLowerPriority
7+
value: 3000

‎versions/v0.1.0/templates/koord-mid.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
apiVersion: scheduling.k8s.io/v1
2+
description: Nearline computation jobs whose SLO weaker than koord-prod.
3+
kind: PriorityClass
4+
metadata:
5+
name: koord-mid
6+
preemptionPolicy: PreemptLowerPriority
7+
value: 7000

‎versions/v0.1.0/templates/koord-prod.yaml‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
apiVersion: scheduling.k8s.io/v1
2+
description: Online production system for applications and businesses.
3+
kind: PriorityClass
4+
metadata:
5+
name: koord-prod
6+
preemptionPolicy: PreemptLowerPriority
7+
value: 9000

‎versions/v0.1.0/values.yaml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ featureGates: ""
1616
koordlet:
1717
image:
1818
repository: koordinatorsh/koordlet
19-
tag: HEAD-ef18acd
19+
tag: v0.1.0-bf37294
2020
resources:
2121
limits:
2222
cpu: 500m
@@ -37,7 +37,7 @@ manager:
3737
replicas: 2
3838
image:
3939
repository: koordinatorsh/koord-manager
40-
tag: HEAD-ef18acd
40+
tag: v0.1.0-bf37294
4141
webhook:
4242
port: 9876
4343
metrics:
@@ -80,7 +80,7 @@ scheduler:
8080
replicas: 2
8181
image:
8282
repository: koordinatorsh/koord-scheduler
83-
tag: main-e07ad10
83+
tag: v0.1.0-bf37294
8484
port: 10251
8585

8686
# resources of koordinator-manager container

0 commit comments

Comments
 (0)