Hi @unnivkn @Tej_Singh_Rana @Vijin Palazhi and anyone. This is around the custom . . .

Kubernetes-Slack Discussions
#1

Ashwin Dora:
Hi @unnivkn @Tej_Singh_Rana @Vijin Palazhi and anyone. This is around the custom kube-scheduler question. I created the my-scheduler as per the question but it fails. Is it because it using the 10259 port same as the existing scheduler ?

image.png
image.png1034×298 10.9 KB

#2

manas jain:
Try to use --secure-port

#3

Tej_Singh_Rana:
Yes, you are correct. Please change it to different one.

#4

Ashwin Dora:
@Tej_Singh_Rana Yes i will change and try. What is this port which i have highlighted

image.png
image.png588×639 22.2 KB

#5

Tej_Singh_Rana:
I don’t know what changes you have made in your custom scheduler manifest file so please take a look into the solution.

#6

manas jain:
`apiVersion: v1
kind: Pod
metadata:
creationTimestamp: null
labels:
component: kube-scheduler
tier: control-plane
name: my-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=false
    • –scheduler-name=my-scheduler
    • –secure-port=10261
    • –port=0
      image: http://k8s.gcr.io/kube-scheduler:v1.19.0|k8s.gcr.io/kube-scheduler:v1.19.0 imagePullPolicy: IfNotPresent
      livenessProbe:
      failureThreshold: 8
      httpGet:
      host: 127.0.0.1
      path: /healthz
      port: 10261
      scheme: HTTPS
      initialDelaySeconds: 10
      periodSeconds: 10
      timeoutSeconds: 15
      name: my-scheduler
      resources:
      requests:
      cpu: 100m
      startupProbe:
      failureThreshold: 24
      httpGet:
      host: 127.0.0.1
      path: /healthz
      port: 10261
      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: {}`
#7

Tej_Singh_Rana:
> --port int = DEPRECATED: the port on which to serve HTTP insecurely without authentication and authorization. If 0, don’t serve plain HTTP at all. See --secure-port instead. This parameter is ignored if a config file is specified in --config.
Reference - https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/