3fa6821437
This adds the option to request GPUs for kubernetes and openshift pods. Since the resource name depends on the GPU vendor and the cluster installation, this option is left for the user to define it in the node pool. To leverage the ability of some schedulers to use fractional GPUs, the actual GPU value is read as a string. For GPUs, requests and limits cannot be decoupled (cf. https://kubernetes.io/docs/tasks/manage-gpus/scheduling-gpus/), so the same value will be used for requests and limits. Change-Id: Ibe33b06c374a431f164080edb34c3a501c360df7
43 lines
978 B
YAML
43 lines
978 B
YAML
zookeeper-servers:
|
|
- host: {zookeeper_host}
|
|
port: {zookeeper_port}
|
|
chroot: {zookeeper_chroot}
|
|
|
|
zookeeper-tls:
|
|
ca: {zookeeper_ca}
|
|
cert: {zookeeper_cert}
|
|
key: {zookeeper_key}
|
|
|
|
labels:
|
|
- name: pod-default
|
|
- name: pod-custom-cpu
|
|
- name: pod-custom-mem
|
|
- name: pod-custom-storage
|
|
- name: pod-custom-gpu
|
|
|
|
providers:
|
|
- name: kubespray
|
|
driver: kubernetes
|
|
context: admin-cluster.local
|
|
pools:
|
|
- name: main
|
|
default-label-cpu: 2
|
|
default-label-memory: 1024
|
|
default-label-storage: 10
|
|
labels:
|
|
- name: pod-default
|
|
type: pod
|
|
- name: pod-custom-cpu
|
|
type: pod
|
|
cpu: 4
|
|
- name: pod-custom-mem
|
|
type: pod
|
|
memory: 2048
|
|
- name: pod-custom-storage
|
|
type: pod
|
|
storage: 20
|
|
- name: pod-custom-gpu
|
|
type: pod
|
|
gpu-resource: gpu-vendor.example/example-gpu
|
|
gpu: 0.5
|