Kubernetes node events warns about FailedNodeAllocatableEnforcement
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Magnum |
In Progress
|
Undecided
|
Bharat Kunwar |
Bug Description
Kubernetes node events warns about FailedNodeAlloc
Steps to reproduce:
- Deploy kubernetes with the latest branch of queens/stable with following kubernetes config:
Client Version: version.
Server Version: version.
- Run `kubectl describe nodes` on the master node.
Expected result:
No warning
Actual result:
Warning FailedNodeAlloc
Discussion:
This is essentially a kubernetes bug[1]. The presence of the warning doesn't necessarily appear to change the overall behaviour of the cluster. According to the docs[2], `cgroups-per-qos` is supposed to be enabled by default. However, this change is not propagated through in the latest version of kubernetes.
As a workaround, I have attached a patch for magnum. If your cluster is already deployed, ingress into your worker nodes and add/change `--cgroups-
```
KUBELET_
```
Then run `sudo systemctl restart kubelet.service`.
[1] https:/
[2] https:/
description: | updated |
summary: |
- FailedNodeAllocatableEnforcement warning under `kubectl describe nodes` + FailedNodeAllocatableEnforcement warning under kubernetes node events |
summary: |
- FailedNodeAllocatableEnforcement warning under kubernetes node events + kubernetes node events warns about FailedNodeAllocatableEnforcement |
description: | updated |
summary: |
- kubernetes node events warns about FailedNodeAllocatableEnforcement + Kubernetes node events warns about FailedNodeAllocatableEnforcement |
description: | updated |
Fix proposed to branch: stable/queens /review. openstack. org/560952
Review: https:/