https://rancher.com/ logo
Join Slack
Powered by
Hi there - I'm struggling a bit with enabling a fe...
# k3s
b
Hi there - I'm struggling a bit with enabling a feature gate on my cluster. I've created the directory 
/etc/rancher/k3s/config.yaml.d/
and added 
0001-enable-device-plugin.yaml
with contents:
shell Copy code
# Enable the Device Plugin feature gate
kubelet-arg:
  - feature-gates=DevicePluginCDIDevices=true
kube-apiserver-arg:
  - feature-gates=DevicePluginCDIDevices=true
Then I've restarted the master node like so 
sudo service k3s restart
. It seems like the cluster should pick up this config but I'm not seeing it (or not looking in the right place) I'm attempting to leverage this plugin - https://gitlab.com/arm-research/smarter/smarter-device-manager , the DaemonSet is running successfully but giving me an error about a feature gate, which is how I've ended up here. 
Could not contact Kubelet, retrying. Did you enable the device plugin feature gate?
(error generated here: https://gitlab.com/arm-research/smarter/smarter-device-manager/-/blob/master/main.go?ref_type=heads#L245)
Ok, I confirmed that these flags are added to the 
kubeadm
process by looking at the logs 
journalctl -u k3s -e
. This is probably out of scope for this channel at this point, I'll probably have to direct this to the GitLab group for the plugin I am using. The problem I am trying to solve is the following: - I have 
/dev/**
resources on each k3s node. I want to allocate those resources and make these resources available to pods. If anyone has a better way let me know :)
4 Views
Open in Slack
PreviousNext
Powered by