pod can not scheduler ,no event,kube-scheduler panic #853
Assignees
Labels
kind/bug
Categorizes issue or PR as related to a bug.
lifecycle/rotten
Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Comments
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
k8s-ci-robot
added
the
lifecycle/stale
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
k8s-ci-robot
added
lifecycle/rotten
|
/assign |
|
Hi @13567436138 The panic issue has been fixed in #910 As for the scheduling issue you mentioned, I’ve verified that everything works as expected. You can use the following configuration to validate it yourself: apiVersion: v1
kind: ServiceAccount
metadata:
name: trimaran-scheduler
namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
name: trimaran-scheduler
roleRef:
kind: ClusterRole
name: cluster-admin
apiGroup: rbac.authorization.k8s.io
subjects:
- kind: ServiceAccount
name: trimaran-scheduler
namespace: kube-system
---
apiVersion: v1
kind: ConfigMap
metadata:
name: trimaran-scheduler
namespace: kube-system
data:
config.yaml: |
apiVersion: kubescheduler.config.k8s.io/v1
kind: KubeSchedulerConfiguration
leaderElection:
leaderElect: false
profiles:
- schedulerName: trimaran-scheduler
plugins:
score:
disabled:
- name: NodeResourcesBalancedAllocation
- name: NodeResourcesFit
enabled:
- name: LoadVariationRiskBalancing
pluginConfig:
- name: LoadVariationRiskBalancing
args:
metricProvider:
type: KubernetesMetricsServer
safeVarianceMargin: 1
safeVarianceSensitivity: 2
---
apiVersion: apps/v1
kind: Deployment
metadata:
name: trimaran-scheduler
namespace: kube-system
spec:
replicas: 1
selector:
matchLabels:
app: trimaran-scheduler
template:
metadata:
labels:
app: trimaran-scheduler
spec:
containers:
- name: kube-scheduler
image: registry.cn-hangzhou.aliyuncs.com/hxpdocker/scheduler-plugins:v1.31
imagePullPolicy: IfNotPresent
command:
- /bin/scheduler
- --config=/etc/kubernetes/config.yaml
volumeMounts:
- name: config-volume
mountPath: /etc/kubernetes
serviceAccountName: trimaran-scheduler
volumes:
- name: config-volume
configMap:
name: trimaran-schedulerEverything is working as expected: $ kubectl -n kube-system logs -f trimaran-scheduler-7cd88d4d5f-mz4cd
I0521 06:50:42.691498 1 serving.go:386] Generated self-signed cert in-memory
W0521 06:50:42.692420 1 client_config.go:659] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
W0521 06:50:43.295056 1 client_config.go:659] Neither --kubeconfig nor --master was specified. Using the inClusterConfig. This might not work.
time="2025-05-21T06:50:43Z" level=info msg="Started watching metrics"
I0521 06:50:43.317921 1 server.go:167] "Starting Kubernetes Scheduler" version="v0.0.0-master+$Format:%H$"
I0521 06:50:43.317970 1 server.go:169] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
I0521 06:50:43.323685 1 requestheader_controller.go:172] Starting RequestHeaderAuthRequestController
I0521 06:50:43.323739 1 shared_informer.go:313] Waiting for caches to sync for RequestHeaderAuthRequestController
I0521 06:50:43.323735 1 configmap_cafile_content.go:205] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::client-ca-file"
I0521 06:50:43.323918 1 shared_informer.go:313] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0521 06:50:43.323747 1 configmap_cafile_content.go:205] "Starting controller" name="client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file"
I0521 06:50:43.323957 1 shared_informer.go:313] Waiting for caches to sync for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0521 06:50:43.324172 1 secure_serving.go:213] Serving securely on [::]:10259
I0521 06:50:43.324268 1 tlsconfig.go:243] "Starting DynamicServingCertificateController"
I0521 06:50:43.424109 1 shared_informer.go:320] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::client-ca-file
I0521 06:50:43.424121 1 shared_informer.go:320] Caches are synced for client-ca::kube-system::extension-apiserver-authentication::requestheader-client-ca-file
I0521 06:50:43.424141 1 shared_informer.go:320] Caches are synced for RequestHeaderAuthRequestControllerThe scheduling events of the pod are as follows: $ kubectl describe pod nginx-6c8c6c4544-trhjz
Name: nginx-6c8c6c4544-trhjz
Namespace: default
......
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 3m50s trimaran-scheduler Successfully assigned default/nginx-6c8c6c4544-trhjz to docker-desktop
Normal Pulling 3m49s kubelet Pulling image "nginx"
Normal Pulled 3m47s kubelet Successfully pulled image "nginx" in 2.565766563s (2.565801711s including waiting)
Normal Created 3m47s kubelet Created container nginx
Normal Started 3m47s kubelet Started container nginx |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Area
Other components
No response
What happened?
W0112 06:23:27.624803 12 client_config.go:664] error creating inClusterConfig, falling back to default config: open /var/run/secrets/kubernetes.io/serviceaccount/token: no such file or directory
What did you expect to happen?
pod can scheduler
How can we reproduce it (as minimally and precisely as possible)?
No response
Anything else we need to know?
No response
Kubernetes version
Scheduler Plugins version
The text was updated successfully, but these errors were encountered: