-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding Intel contributions to k8s stack #16
Comments
krsna1729
added a commit
that referenced
this issue
Jan 1, 2019
Fixes: #8, #16 Setting CPUManager=static allows `Guaranteed` QoS class workloads to get cpu isolation and affinity benefits. https://kubernetes.io/blog/2018/07/24/feature-highlight-cpu-manager/ Setting reserved compute resources for system processes and critical kube components prevents from DoS'ing the compute node. https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
krsna1729
added a commit
that referenced
this issue
Jan 1, 2019
Fixes: #8, #16 Setting CPUManager=static allows `Guaranteed` QoS class workloads to get cpu isolation and affinity benefits. https://kubernetes.io/blog/2018/07/24/feature-highlight-cpu-manager/ Setting reserved compute resources for system processes and critical kube components prevents from DoS'ing the compute node. https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
krsna1729
added a commit
that referenced
this issue
Jan 1, 2019
Fixes: #8, #16 Setting CPUManager=static allows `Guaranteed` QoS class workloads to get cpu isolation and affinity benefits. https://kubernetes.io/blog/2018/07/24/feature-highlight-cpu-manager/ Setting reserved compute resources for system processes and critical kube components prevents from DoS'ing the compute node. https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
krsna1729
added a commit
that referenced
this issue
Jan 2, 2019
Fixes: #8, #16 Setting CPUManager=static allows `Guaranteed` QoS class workloads to get cpu isolation and affinity benefits. https://kubernetes.io/blog/2018/07/24/feature-highlight-cpu-manager/ Setting reserved compute resources for system processes and critical kube components prevents from DoS'ing the compute node. https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
mcastelino
pushed a commit
that referenced
this issue
Jan 2, 2019
Fixes: #8, #16 Setting CPUManager=static allows `Guaranteed` QoS class workloads to get cpu isolation and affinity benefits. https://kubernetes.io/blog/2018/07/24/feature-highlight-cpu-manager/ Setting reserved compute resources for system processes and critical kube components prevents from DoS'ing the compute node. https://kubernetes.io/docs/tasks/administer-cluster/reserve-compute-resources/ Signed-off-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
We also have: and maybe later: |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@mcastelino /cc @amshinde
Add an upgraded version of amshinde/kata-sriov-dp which has example manifests for deploying Multus-CNI, SRIOV-CNI and sriov device plugin. Optionally, include manifests for intel-device-plugins-for-kubernetes and userspace-cni-network-plugin
Also look into enabling CPUManager by default in the kubelet configuration along with #8
The text was updated successfully, but these errors were encountered: