no kube-reserved and/or system-reserved for kubelet config

[panpan0000]

Describe the version
version about:

1. kubean : v0.4.4-rc1

Describe the bug

there's no any xxx_reserved parameters in /conf/group_vars.yml

In the cluster created by kubean,
kubectl describe no :

• the Allocatable CPU is all CPU
• and the memory is ALL - 100M.
  which is not good and not safe , as state in (Re-)Enable resource reservation by default for core components and host container runtime kubernetes-sigs/kubespray#9692

Expected behavior
(1) add default value in group_vars.yml ? (it's hard... no value is silver bullet.. but kube_master_xxx_erserved may be necessary )
(2)expose the parameter which user can set it for below parameters:

# Optionally reserve this space for kube daemons.
# kube_reserved: true
## Uncomment to override default values
## The following two items need to be set when kube_reserved is true
# kube_reserved_cgroups_for_service_slice: kube.slice
# kube_reserved_cgroups: "/{{ kube_reserved_cgroups_for_service_slice }}"
# kube_memory_reserved: 256Mi
# kube_cpu_reserved: 100m
# kube_ephemeral_storage_reserved: 2Gi
# kube_pid_reserved: "1000"
# Reservation for master hosts
# kube_master_memory_reserved: 512Mi
# kube_master_cpu_reserved: 200m
# kube_master_ephemeral_storage_reserved: 2Gi
# kube_master_pid_reserved: "1000"

[wenting-guo]

/kind feature

[github-actions]

This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. Maintainers can add the exempt-stale label.

[github-actions]

This issue has been automatically closed because we haven't received a response from the original author 🙈. This automation helps keep the issue tracker clean from issues that are unactionable. Please reach out if you have more information for us! 🙂