-
Notifications
You must be signed in to change notification settings - Fork 116
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
sriov-network-config-daemon deployment failed with error: "failed to load kubelet kubeconfig: open /host/etc/kubernetes/kubeconfig: no such file or directory" #48
Labels
bug
Something isn't working
Comments
The path (/host/etc/kubernetes/kubeconfig) only exists on openshift, looks like you're using openshift images on k8s environment. |
moshe010
added a commit
to moshe010/sriov-network-operator
that referenced
this issue
Jan 27, 2021
PR 51 try to fix it by adding the CLUSTER_TYPE=kubernetes in Makefile which is wrong. The CLUSTER_TYPE=kubernetes should be exposed in the sriov-operator and sriov-network-config-daemon Pods so that they will behave according to the cluster type This commit fix it by removing the CLUSTER_TYPE=kubernetes from the Makefile and add it to sriov-operator and .sriov-network-config-daemon Dockerfile. Fixes: k8snetworkplumbingwg#48
moshe010
added a commit
to moshe010/sriov-network-operator
that referenced
this issue
Jan 27, 2021
PR 51 try to fix it by adding the CLUSTER_TYPE=kubernetes in Makefile which is wrong. The CLUSTER_TYPE=kubernetes should be exposed in the sriov-operator and sriov-network-config-daemon Pods so that they will behave according to the cluster type This commit fix it by removing the CLUSTER_TYPE=kubernetes from the Makefile and add it to sriov-operator and .sriov-network-config-daemon Dockerfile. Fixes: k8snetworkplumbingwg#48 Signed-off-by: Moshe Levi <[email protected]>
moshe010
added a commit
to moshe010/sriov-network-operator
that referenced
this issue
Jan 28, 2021
PR 51 try to fix it by adding the CLUSTER_TYPE=kubernetes in Makefile which is wrong. The CLUSTER_TYPE=kubernetes should be exposed in the sriov-operator and sriov-network-config-daemon Pods so that they will behave according to the cluster type This commit fix it by removing the CLUSTER_TYPE=kubernetes from the Makefile and add it to sriov-operator and .sriov-network-config-daemon Dockerfile. Fixes: k8snetworkplumbingwg#48 Signed-off-by: Moshe Levi <[email protected]>
rollandf
added a commit
to rollandf/sriov-network-operator
that referenced
this issue
Feb 2, 2025
ci: add all changed file to PR
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Deployment operator failed on sriov-network-config-daemon deployment stage with error:
failed to load kubelet kubeconfig: open /host/etc/kubernetes/kubeconfig: no such file or directory
Setup info:
OS - Ubuntu 18.04
Vanilla K8s - 1.17.5
SRIOV operator - github master
K8s cluster pods:
Error log:
The text was updated successfully, but these errors were encountered: