☰

多个 kube-scheduler

tag-icon • tag-icon kubernetes
多个 kube-scheduler

我正在尝试创建一个 kube-shceduler，供我的组织 pod 部署（数据中心）使用。目标是让任何部署的 pod 在数据中心的两个站点之间平均分配。为了实现这一点，我创建了一个新的 kube-shceduler 清单（见下文），在其中我更改了使用的端口并使用该--config参数添加了一个新配置文件（见下文）。问题是，即使将--port参数设置为原始 kube-scheduler 尚未使用的新端口，它仍会尝试使用旧端口。因此，新的 kube 调度程序无法启动：

I1109 20:27:59.225996       1 registry.go:173] Registering SelectorSpread plugin
I1109 20:27:59.226097       1 registry.go:173] Registering SelectorSpread plugin
I1109 20:27:59.926994       1 serving.go:331] Generated self-signed cert in-memory
failed to create listener: failed to listen on 0.0.0.0:10251: listen tcp 0.0.0.0:10251: bind: address already in use

我如何强制使用指定的端口或如何删除原始的 kube-scheduler，以便两者之间不会发生任何冲突。第一种解决方案是可取的。

配置 kube-scheduler（清单 - /etc/kubernetes/manifest/kube-scheduler.yaml）：

apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    component: kube-scheduler
    tier: control-plane
  name: kube-scheduler
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-scheduler
    - --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
    - --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
    - --bind-address=127.0.0.1
    - --kubeconfig=/etc/kubernetes/scheduler.conf
    - --leader-elect=true
      #- --port=0
    image: k8s.gcr.io/kube-scheduler:v1.19.3
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10259
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
    name: kube-scheduler
    resources:
      requests:
        cpu: 100m
    startupProbe:
      failureThreshold: 24
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10259
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
    volumeMounts:
    - mountPath: /etc/kubernetes/scheduler.conf
      name: kubeconfig
      readOnly: true
  hostNetwork: true
  priorityClassName: system-node-critical
  volumes:
  - hostPath:
      path: /etc/kubernetes/scheduler.conf
      type: FileOrCreate
    name: kubeconfig
status: {}

配置kube-custom-scheduler.yaml（/etc/kubernetes/manifest/kube-custom-scheduler.yaml）：

apiVersion: v1
kind: Pod
metadata:
  creationTimestamp: null
  labels:
    component: kube-custom-scheduler
    tier: control-plane
  name: kube-custom-scheduler
  namespace: kube-system
spec:
  containers:
  - command:
    - kube-scheduler 
    - --config=/etc/kubernetes/scheduler-custom.conf
    - --master=true
    - --authentication-kubeconfig=/etc/kubernetes/scheduler.conf
    - --authorization-kubeconfig=/etc/kubernetes/scheduler.conf
    - --bind-address=127.0.0.1
    - --kubeconfig=/etc/kubernetes/scheduler.conf
    - --leader-elect=false
    - --secure-port=10269
    - --scheduler-name=kube-custom-shceduler
    - --port=10261
    image: k8s.gcr.io/kube-scheduler:v1.19.3
    imagePullPolicy: IfNotPresent
    livenessProbe:
      failureThreshold: 8
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10269
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
    name: kube-scheduler
    resources:
      requests:
        cpu: 100m
    startupProbe:
      failureThreshold: 24
      httpGet:
        host: 127.0.0.1
        path: /healthz
        port: 10269
        scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
    volumeMounts:
    - mountPath: /etc/kubernetes/scheduler.conf
      name: kubeconfig
      readOnly: true
    - mountPath: /etc/kubernetes/scheduler-custom.conf
      name: customconfig
      readOnly: true
  hostNetwork: true
  priorityClassName: system-node-critical
  volumes:
  - hostPath:
      path: /etc/kubernetes/scheduler.conf
      type: FileOrCreate
    name: kubeconfig
  - hostPath:
      path: /etc/kubernetes/scheduler-custom.conf
      type: FileOrCreate
    name: customconfig 
status: {}

kube-custom-scheduler.yaml（/etc/kubernetes/scheduler-custom.conf）中提到的自定义配置：

apiVersion: kubescheduler.config.k8s.io/v1beta1
kind: KubeSchedulerConfiguration

profiles:
  - pluginConfig:
      - name: PodTopologySpread
        args:
          defaultConstraints:
            - maxSkew: 1
              topologyKey: topology.kube.io/datacenter 
              whenUnsatisfiable: ScheduleAnyway

如果您需要有关该集群的更多信息，请不要犹豫。

PS：截至今天，我无法让默认（不安全）端口的覆盖正常工作。我转向了另一种替代方案来实现目标。我创建了一个准入控制器（Kyverno），它将通过向每个部署添加“podtopologyspread”字段来改变部署/Pods 文件。因此，现在每个部署的 pod 都将根据准入控制器定义的规则分配给数据中心中存在的两个站点之一。如果有人成功更改了默认 Kube-Scheduller 的配置，我很想知道您是如何做到的。

答案1

根据官方文档，--port标志已被弃用，因此很有可能在您的版本中Kubernetes它不再起作用了：

--port int     Default: 10251

已弃用：未经身份验证和授权而以不安全方式提供 HTTP 服务的端口。如果为 0，则根本不提供纯 HTTP 服务。 请参阅--secure-port。

相关内容