Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

management-workload-partitioning: update kubelet config file name #726

Merged
merged 1 commit into from
Apr 8, 2021
Merged

management-workload-partitioning: update kubelet config file name #726

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions enhancements/management-workload-partitioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -531,7 +531,7 @@ indicator to configure the CPU shares as BestEffort.
#### Kubelet Changes

Kubelet will be changed to look for a configuration file,
`/etc/kubernetes/workload-pinning`, to enable the management
`/etc/kubernetes/openshift-workload-pinning`, to enable the management
workload partitioning feature. The file should contain the cpuset
specifier for the CPUs making up each CPU pool.

Expand Down Expand Up @@ -579,7 +579,7 @@ spec:
source: data:text/plain;charset=utf-8;base64,encoded-content-here
mode: 420
overwrite: true
path: /etc/kubernetes/workload-pinning
path: /etc/kubernetes/openshift-workload-pinning
user:
name: root
```
Expand All @@ -595,7 +595,7 @@ annotation_prefix = "io.openshift.workload.management"
resources = { "cpushares" = "", "cpuset" = "0-1,52-53" }
```

The contents of `/etc/kubernetes/workload-pinning` should look like
The contents of `/etc/kubernetes/openshift-workload-pinning` should look like
this:

```json
Expand Down Expand Up @@ -832,7 +832,7 @@ manifest to configure CRI-O so that containers from pods with the
CPU set specified by the management workload settings.

The installer will be changed to create a machine config manifest to
write the `/etc/kubernetes/management-pinning` configuration file for
write the `/etc/kubernetes/openshift-workload-pinning` configuration file for
kubelet. The file will have SELinux settings configured so that it is
only readable by the kubelet.

Expand Down