You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The k8s cluster is a highly available cluster that uses helm to deploy scheduler plugins as the second scheduler. Setting the leaderElect parameter to true and the replicatCount parameter to 3 will cause pod scheduling to remain in a pending state, with no pods or events displayed. Podgroups resources will be in a scheduling state
Afterwards, I configured the leaderElect parameter to flag and the replicCount parameter to 1, and the pod scheduling was normal
What did you expect to happen?
I hope to deploy scheduler plugins as the second scheduler using helm in the k8s high availability cluster, with the leaderElect parameter set to true and the replicatCount parameter set to 3, and pod scheduling functioning properly
How can we reproduce it (as minimally and precisely as possible)?
A highly available k8s cluster, version 1.29.5
Schedule plugins in version 1.29.7
Deploying scheduler plugins as a secondary scheduler using Helm
The value. yaml configuration is as follows
# Default values for scheduler-plugins-as-a-second-scheduler.# This is a YAML-formatted file.# Declare variables to be passed into your templates.scheduler:
name: scheduler-plugins-schedulerimage: registry.k8s.io/scheduler-plugins/kube-scheduler:v0.29.7replicaCount: 3leaderElect: truenodeSelector: {}affinity: {}tolerations: []controller:
name: scheduler-plugins-controllerimage: registry.k8s.io/scheduler-plugins/controller:v0.29.7replicaCount: 3nodeSelector: {}affinity: {}tolerations: []# LoadVariationRiskBalancing and TargetLoadPacking are not enabled by default# as they need extra RBAC privileges on metrics.k8s.io.plugins:
enabled: ["NodeResourcesAllocatable"]disabled: [] # only in-tree plugins need to be defined here# Customize the enabled plugins' config.# Refer to the "pluginConfig" section of manifests/<plugin>/scheduler-config.yaml.# For example, for Coscheduling plugin, you want to customize the permit waiting timeout to 10 seconds:pluginConfig:
#- name: Coscheduling# args:# permitWaitingTimeSeconds: 10 # default is 60# Or, customize the other plugins# - name: NodeResourceTopologyMatch# args:# scoringStrategy:# type: MostAllocated # default is LeastAllocated#- name: SySched# args:# defaultProfileNamespace: "default"# defaultProfileName: "full-seccomp"
- name: NodeResourcesAllocatableargs:
mode: Leastresources:
- name: hygon.com/dcuweight: 100
Anything else we need to know?
k8s cluster
I have removed the taint for the master02 and master03 nodes of k8s
Area
Other components
No response
What happened?
The k8s cluster is a highly available cluster that uses helm to deploy scheduler plugins as the second scheduler. Setting the leaderElect parameter to true and the replicatCount parameter to 3 will cause pod scheduling to remain in a pending state, with no pods or events displayed. Podgroups resources will be in a scheduling state
Afterwards, I configured the leaderElect parameter to flag and the replicCount parameter to 1, and the pod scheduling was normal
What did you expect to happen?
I hope to deploy scheduler plugins as the second scheduler using helm in the k8s high availability cluster, with the leaderElect parameter set to true and the replicatCount parameter set to 3, and pod scheduling functioning properly
How can we reproduce it (as minimally and precisely as possible)?
A highly available k8s cluster, version 1.29.5
Schedule plugins in version 1.29.7
Deploying scheduler plugins as a secondary scheduler using Helm
The value. yaml configuration is as follows
Anything else we need to know?
k8s cluster
I have removed the taint for the master02 and master03 nodes of k8s
podgroup info
scheduler-plugins config
node resources
scheduler-plugins-scheduler logs
podgroup info
Kubernetes version
Scheduler Plugins version
The text was updated successfully, but these errors were encountered: