k3s/pkg/apis/componentconfig/v1alpha1
Kubernetes Submit Queue 69ce7d8475 Merge pull request #44606 from ivan4th/fix-serialization-of-enforce-node-allocatable
Automatic merge from submit-queue (batch tested with PRs 44606, 46038)

Fix serialization of EnforceNodeAllocatable

EnforceNodeAllocatable being `nil` and `[]` are treated in different
ways by kubelet. Namely, `nil` is replaced with `[]string{"pods"}` by
the defaulting mechanism.

E.g. if you run kubelet in Docker-in-Docker environment
you may need to run it with the following options:
`--cgroups-per-qos=false --enforce-node-allocatable=`
(this corresponds to EnforceNodeAllocatable being empty array and not
null) If you then grab kubelet configuration via /configz and try to
reuse it for dynamic kubelet config, kubelet will think that
EnforceNodeAllocatable is null, failing to run in the
Docker-in-Docker environment.

Encountered this while updating Virtlet for Kubernetes 1.6
(the dev environment is based on kubeadm-dind-cluster)
2017-05-19 11:52:03 -07:00
..
BUILD Update generated 2017-05-15 10:01:57 -05:00
defaults.go Update to plumb through configurable locking on different resource types. 2017-05-15 10:01:46 -05:00
defaults_test.go Add a utility to convert componentconfig into a configmap 2017-05-08 15:18:27 -05:00
doc.go Flag all packages as needing defaulters 2016-10-18 21:07:33 -04:00
register.go Remove redundent GetObjectKind() defined on top-level types 2017-05-04 10:31:58 -07:00
types.go Merge pull request #44606 from ivan4th/fix-serialization-of-enforce-node-allocatable 2017-05-19 11:52:03 -07:00
zz_generated.conversion.go Merge pull request #44606 from ivan4th/fix-serialization-of-enforce-node-allocatable 2017-05-19 11:52:03 -07:00
zz_generated.deepcopy.go Update generated files 2017-05-17 00:59:52 -07:00
zz_generated.defaults.go start the apimachinery repo 2017-01-11 09:09:48 -05:00