adamant-intern-34485
06/12/2025, 9:45 AM--default-runtime=nvidia
to the K3S cli. In a regular install this is done by adding it to the ExecStart
parameter of /etc/systemd/system/k3s.service
• Set the following label to the node: <http://nvidia.com/gpu.present=true|nvidia.com/gpu.present=true>
.agreeable-window-17829
06/12/2025, 2:02 PMbig-television-41348
06/12/2025, 3:23 PMable-lock-7461
06/12/2025, 6:17 PMcreamy-pencil-82913
06/12/2025, 6:32 PMcreamy-pencil-82913
06/12/2025, 6:34 PMable-lock-7461
06/12/2025, 6:39 PMnumerous-island-90629
06/13/2025, 6:29 AMwaiting for probes: kube-scheduler
. I have tried reinstalling as well that didn't help either.
I have attached screenshot of provisioning logscareful-dress-15206
06/13/2025, 10:24 AMcareful-dress-15206
06/13/2025, 11:34 AMhundreds-evening-84071
06/13/2025, 1:46 PMkubectl auth can-i get pods --all-namespaces --as my-service-account
What am I missing?
apiVersion: v1
kind: ServiceAccount
metadata:
name: my-service-account
namespace: default # You can specify any namespace you prefer
---
apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
kind: ClusterRole
metadata:
name: get-pods-clusterrole
rules:
- apiGroups: [""]
resources: ["pods"]
verbs: ["get", "list"]
---
apiVersion: <http://rbac.authorization.k8s.io/v1|rbac.authorization.k8s.io/v1>
kind: ClusterRoleBinding
metadata:
name: get-pods-clusterrolebinding
subjects:
- kind: ServiceAccount
name: my-service-account
namespace: default # Use the same namespace where the service account was created
roleRef:
kind: ClusterRole
name: get-pods-clusterrole
apiGroup: <http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>
boundless-soccer-78417
06/15/2025, 2:24 AMnarrow-guitar-87575
06/15/2025, 9:30 AMdamp-optician-31010
06/16/2025, 2:13 AMdamp-optician-31010
06/16/2025, 2:15 AMdamp-optician-31010
06/16/2025, 2:16 AMdamp-optician-31010
06/16/2025, 11:23 AMdamp-optician-31010
06/16/2025, 9:21 PMdamp-optician-31010
06/16/2025, 9:21 PMdamp-optician-31010
06/16/2025, 9:22 PMdamp-optician-31010
06/16/2025, 9:23 PMsome-apple-96240
06/17/2025, 12:30 PMastonishing-address-98404
06/17/2025, 4:24 PMbored-farmer-36655
06/17/2025, 4:58 PMastonishing-address-98404
06/17/2025, 5:01 PMastonishing-address-98404
06/17/2025, 5:03 PMbored-farmer-36655
06/17/2025, 5:50 PMastonishing-address-98404
06/17/2025, 5:52 PMbored-farmer-36655
06/17/2025, 5:56 PMastonishing-address-98404
06/17/2025, 5:58 PM