Skip to content

Instantly share code, notes, and snippets.

@akutz
Last active May 17, 2019 08:07
Show Gist options
  • Save akutz/4cdbea384de1fa0f7fa6deb0d5e8ee2c to your computer and use it in GitHub Desktop.
Save akutz/4cdbea384de1fa0f7fa6deb0d5e8ee2c to your computer and use it in GitHub Desktop.
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.0-alpha.0.1223+7bfd0d358cbe9e", GitCommit:"7bfd0d358cbe9eb1e8dc81c909ae9d03705ec438", GitTreeState:"clean", BuildDate:"2018-09-11T16:26:36Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"13+", GitVersion:"v1.13.0-alpha.0.1223+7bfd0d358cbe9e", GitCommit:"7bfd0d358cbe9eb1e8dc81c909ae9d03705ec438", GitTreeState:"clean", BuildDate:"2018-09-11T16:23:05Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"}
apiVersion: componentconfig/v1alpha1
kind: KubeSchedulerConfiguration
clientConnection:
kubeconfig: /var/lib/kube-scheduler/kubeconfig
leaderElection:
leaderElect: true
[0]akutz@k8s-c01-ci-latest:~$ sudo journalctl -xefu kube-scheduler
-- Logs begin at Tue 2018-09-11 15:23:42 CDT. --
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci systemd[1]: Started Kubernetes Scheduler.
-- Subject: Unit kube-scheduler.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kube-scheduler.service has finished starting up.
--
-- The start-up result is done.
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci systemd[1]: Starting Kubernetes Scheduler...
-- Subject: Unit kube-scheduler.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit kube-scheduler.service has begun starting up.
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090666 11347 flags.go:33] FLAG: --address="0.0.0.0"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090719 11347 flags.go:33] FLAG: --algorithm-provider=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090724 11347 flags.go:33] FLAG: --alsologtostderr="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090730 11347 flags.go:33] FLAG: --config="/var/lib/kube-scheduler/kube-scheduler-config.yaml"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090735 11347 flags.go:33] FLAG: --contention-profiling="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090740 11347 flags.go:33] FLAG: --failure-domains="kubernetes.io/hostname,failure-domain.beta.kubernetes.io/zone,failure-domain.beta.kubernetes.io/region"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090748 11347 flags.go:33] FLAG: --feature-gates=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090754 11347 flags.go:33] FLAG: --hard-pod-affinity-symmetric-weight="1"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090759 11347 flags.go:33] FLAG: --help="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090763 11347 flags.go:33] FLAG: --kube-api-burst="100"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090767 11347 flags.go:33] FLAG: --kube-api-content-type="application/vnd.kubernetes.protobuf"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090772 11347 flags.go:33] FLAG: --kube-api-qps="50"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090778 11347 flags.go:33] FLAG: --kubeconfig=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090781 11347 flags.go:33] FLAG: --leader-elect="true"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090785 11347 flags.go:33] FLAG: --leader-elect-lease-duration="15s"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090791 11347 flags.go:33] FLAG: --leader-elect-renew-deadline="10s"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090796 11347 flags.go:33] FLAG: --leader-elect-resource-lock="endpoints"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090800 11347 flags.go:33] FLAG: --leader-elect-retry-period="2s"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090804 11347 flags.go:33] FLAG: --lock-object-name="kube-scheduler"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090808 11347 flags.go:33] FLAG: --lock-object-namespace="kube-system"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090812 11347 flags.go:33] FLAG: --log-backtrace-at=":0"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090818 11347 flags.go:33] FLAG: --log-dir=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090822 11347 flags.go:33] FLAG: --log-flush-frequency="5s"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090826 11347 flags.go:33] FLAG: --logtostderr="true"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090829 11347 flags.go:33] FLAG: --master=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci systemd[1]: kube-scheduler.service: main process exited, code=exited, status=1/FAILURE
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090833 11347 flags.go:33] FLAG: --policy-config-file=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090837 11347 flags.go:33] FLAG: --policy-configmap=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090841 11347 flags.go:33] FLAG: --policy-configmap-namespace="kube-system"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090845 11347 flags.go:33] FLAG: --port="10251"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090850 11347 flags.go:33] FLAG: --profiling="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090854 11347 flags.go:33] FLAG: --scheduler-name="default-scheduler"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090859 11347 flags.go:33] FLAG: --stderrthreshold="2"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090863 11347 flags.go:33] FLAG: --use-legacy-policy-config="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090866 11347 flags.go:33] FLAG: --v="2"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090870 11347 flags.go:33] FLAG: --version="false"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090876 11347 flags.go:33] FLAG: --vmodule=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: I0911 15:25:10.090880 11347 flags.go:33] FLAG: --write-config-to=""
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci kube-scheduler[11347]: no kind "KubeSchedulerConfiguration" is registered for version "componentconfig/v1alpha1" in scheme "k8s.io/kubernetes/pkg/scheduler/apis/config/scheme/scheme.go:29"
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci systemd[1]: Unit kube-scheduler.service entered failed state.
Sep 11 15:25:10 k8s-c01-ci-latest.vmware.ci systemd[1]: kube-scheduler.service failed.
[Unit]
Description=Kubernetes Scheduler
Documentation=https://github.com/kubernetes/kubernetes
After=kube-apiserver.service
Requires=kube-apiserver.service
[Install]
WantedBy=multi-user.target
[Service]
Restart=on-failure
RestartSec=5
WorkingDirectory=/var/lib/kube-scheduler
EnvironmentFile=/etc/default/kube-scheduler
ExecStart=/opt/bin/kube-scheduler $SCHEDULER_OPTS
@kaiser1103
Copy link

did you fix it ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment