kamaji

kamaji copied to clipboard

The current Kamaji specification doesn't allow specific extra arguments for the kubelet, although kubeadm supports it.

KubeletExtraArgs passes through extra arguments to the kubelet.
The arguments here are passed to the kubelet command line via the environment file kubeadm writes at runtime for the kubelet to source. 
This overrides the generic base-level configuration in the kubelet-config ConfigMap
Flags have higher priority when parsing. These values are local and specific to the node kubeadm is executing on.
A key in this map is the flag name as it appears on the command line except without leading dash(es).

This feature seems unfeasible for Kamaji, since as the docs is stating:

These values are local and specific to the node kubeadm is executing on.

However, we could change this issue in order to remove any reference from the current code base to the NodeRegistrationOptions struct that is used by the end-user while launching the kubeadm command since we're only storing the ClusterConfiguration that will be used by the command.