Skip to content

Commit

Permalink
Correct Helm Chart Docs For Container Requests and Limits
Browse files Browse the repository at this point in the history 
The resources.cpuRequest and resources.memoryRequest varialbes are
not valid in the helm chart values.yaml file. The correct varialbe
name for setting the requests and limits is resources.

Also, fixed white space alignment in the markdown table.
  • Loading branch information
(Brien Dieterle) committed Mar 13, 2021
1 parent 9ff1875 commit d62ec1d
Showing 1 changed file with 2 additions and 3 deletions.
5 changes: 2 additions & 3 deletions charts/descheduler/README.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -59,8 +59,7 @@ The following table lists the configurable parameters of the _descheduler_ chart
| `priorityClassName` | The name of the priority class to add to pods | `system-cluster-critical` |
| `rbac.create` | If `true`, create & use RBAC resources | `true` |
| `podSecurityPolicy.create` | If `true`, create PodSecurityPolicy | `true` |
| `resources.cpuRequest` | Descheduler container CPU request | `500m` |
| `resources.memoryRequest` | Descheduler container memory request | `256Mi` |
| `resources` | Descheduler container CPU and memory requests/limits | _see values.yaml_ |
| `serviceAccount.create` | If `true`, create a service account for the cron job | `true` |
| `serviceAccount.name` | The name of the service account to use, if not set and create is true a name is generated using the fullname template | `nil` |
| `nodeSelector` | Node selectors to run the descheduler cronjob on specific nodes | `nil` |
| `nodeSelector` | Node selectors to run the descheduler cronjob on specific nodes | `nil` |

0 comments on commit d62ec1d

Please sign in to comment.