You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: deployment/pcm/README.md
+29-27Lines changed: 29 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,13 +7,13 @@ Helm chart instructions
7
7
- Configurable as non-privileged container (value: `privileged=false` / default) and privileged container,
8
8
- Support for bare-metal and VM host configurations (files: [values-metal.yaml](values-metal.yaml), [values-vm.yaml](values-metal.yaml)),
9
9
- Ability to deploy multiple releases alongside configured differently to handle different kinds of machines (bare-metal, VM) at the [same time](#heterogeneous-mixed-vmmetal-instances-cluster),
10
-
- Controllable set of metrics and method of collection (RDT, uncore), support direct (msr) and indirect (Linux abstractions perf/resctrl) counter accesses (file: `values-indirect.yaml`).
11
-
- Linux Watchdog handling (controlled with PCM_KEEP_NMI_WATCHDOG, PCM_NO_AWS_WORKAROUND, nmiWatchdogMount values).
10
+
- Controllable set of metrics and method of collection (RDT, uncore), support direct (msr) and indirect (Linux abstractions perf/resctrl) counter accesses (file: [values-indirect.yaml](values-indirect.yaml)).
11
+
- Linux Watchdog handling (controlled with `PCM_KEEP_NMI_WATCHDOG`, `PCM_NO_AWS_WORKAROUND`, `nmiWatchdogMount` values).
12
12
- Deploy to own namespace with "helm install ... **-n pcm --create-namespace**"
13
13
14
14
#### Integration features:
15
15
16
-
- node-feature-discovery based nodeSelector and nodeAffinity (values: nfd, nfdBaremetalAffinity, nfdRDTAffinity),
16
+
- node-feature-discovery based nodeSelector and nodeAffinity (values: `nfd`, `nfdBaremetalAffinity`, `nfdRDTAffinity`),
17
17
- Examples for non-privileged mode using device plugin ("smarter-devices-manager") or using NRI device-injector plugin (TODO) (file: [values-smarter-devices-cpu-mem.yaml](values-smarter-devices-cpu-mem.yaml) ),
18
18
- Integration with NRI balloons policy plugin (value: `nriBalloonsPolicyIntegration`),
#### Direct method as non-privileged container (not recommended)
232
217
218
+
**TODO**: TO BE MOVED TO EXTERNAL FILE/SECTION
219
+
233
220
**Note** PCM requires access to /dev/cpu device in read writer mode (MSR access) but it is no possible currently to mount devices in Kubernetes pods/containers in vanila Kubernetes. Please read this isses for more information https://github.com/kubernetes/kubernetes/issues/5607.
234
221
235
222
##### a) Device injection using 3rd party device-plugin
223
+
236
224
237
225
TO run PCM with as non privileged pod, we can third party devices plugins e.g.:
##### b) Device injection using NRI plugin device-injection
250
+
##### b) Device injection using NRI plugin device-injection
263
251
264
-
**TODO**: **Warning** This is work in progress, because it is needed to manually specific all /dev/cpu/XX/msr devices, which is unpractical in production.
252
+
**TODO**: **Warning** This is work in progress, because it is needed to manually specific all /dev/cpu/XX/msr devices, which is unpractical in production (TO BE MOVED TO EXTERNAL FILE).
265
253
266
254
```
267
255
git clone https://github.com/containerd/nri/
@@ -294,7 +282,7 @@ docker exec kind-control-plane systemctl status device-injector
0 commit comments