search

ibuildthecloud / k3v

Virtual Kubernetes
Apache License 2.0
684 stars 28 forks source link

k3v fails while starting kube-controller-manager #4

Open gokulpch opened 5 years ago

gokulpch commented 5 years ago

Hi,

I was trying to start k3v on a cluster installed using Kubeadm. k3v bails out as it tries to use port "10252" which the existing clusters kube-controller-manager is already listening on. Is there a way to change the port through some config?


root@skull3:~# ./k3v
INFO[0000] Starting controller
INFO[0000] Starting k3s
INFO[0000] Running kube-apiserver --secure-port=6444 --tls-cert-file=/root/k3v-data/server/k3v-data/server/tls/serving-kube-apiserver.crt --proxy-client-key-file=/root/k3v-data/server/k3v-data/server/tls/client-auth-proxy.key --requestheader-group-headers=X-Remote-Group --advertise-port=7443 --service-account-issuer=k3s --api-audiences=unknown --basic-auth-file=/root/k3v-data/server/k3v-data/server/cred/passwd --kubelet-client-key=/root/k3v-data/server/k3v-data/server/tls/client-kube-apiserver.key --enable-admission-plugins=NodeRestriction --tls-private-key-file=/root/k3v-data/server/k3v-data/server/tls/serving-kube-apiserver.key --kubelet-client-certificate=/root/k3v-data/server/k3v-data/server/tls/client-kube-apiserver.crt --cert-dir=/root/k3v-data/server/k3v-data/server/tls/temporary-certs --allow-privileged=true --authorization-mode=Node,RBAC --service-cluster-ip-range=10.45.0.0/16 --insecure-port=0 --bind-address=127.0.0.1 --requestheader-allowed-names=system:auth-proxy --proxy-client-cert-file=/root/k3v-data/server/k3v-data/server/tls/client-auth-proxy.crt --requestheader-extra-headers-prefix=X-Remote-Extra- --service-account-signing-key-file=/root/k3v-data/server/k3v-data/server/tls/service.key --service-account-key-file=/root/k3v-data/server/k3v-data/server/tls/service.key --requestheader-client-ca-file=/root/k3v-data/server/k3v-data/server/tls/request-header-ca.crt --requestheader-username-headers=X-Remote-User --client-ca-file=/root/k3v-data/server/k3v-data/server/tls/client-ca.crt
E0721 04:59:45.921586    9503 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.921864    9503 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.921917    9503 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.921967    9503 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.921984    9503 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.922005    9503 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted
W0721 04:59:45.963245    9503 genericapiserver.go:315] Skipping API batch/v2alpha1 because it has no resources.
W0721 04:59:45.970289    9503 genericapiserver.go:315] Skipping API node.k8s.io/v1alpha1 because it has no resources.
E0721 04:59:45.989512    9503 prometheus.go:138] failed to register depth metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.989540    9503 prometheus.go:150] failed to register adds metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.989625    9503 prometheus.go:162] failed to register latency metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.989666    9503 prometheus.go:174] failed to register work_duration metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.989716    9503 prometheus.go:189] failed to register unfinished_work_seconds metric admission_quota_controller: duplicate metrics collector registration attempted
E0721 04:59:45.989732    9503 prometheus.go:202] failed to register longest_running_processor_microseconds metric admission_quota_controller: duplicate metrics collector registration attempted
INFO[0000] Running kube-controller-manager --use-service-account-credentials=true --cluster-cidr=10.44.0.0/16 --cluster-signing-key-file=/root/k3v-data/server/k3v-data/server/tls/server-ca.key --leader-elect=false --controllers=*,-nodeipam,-nodelifecycle,-persistentvolume-binder,-attachdetach,-persistentvolume-expander --port=10252 --secure-port=0 --service-account-private-key-file=/root/k3v-data/server/k3v-data/server/tls/service.key --root-ca-file=/root/k3v-data/server/k3v-data/server/tls/server-ca.crt --bind-address=127.0.0.1 --cluster-signing-cert-file=/root/k3v-data/server/k3v-data/server/tls/server-ca.crt --allocate-node-cidrs=true --kubeconfig=/root/k3v-data/server/k3v-data/server/cred/controller.kubeconfig
failed to create listener: failed to listen on 0.0.0.0:10252: listen tcp 0.0.0.0:10252: bind: address already in use```
texascloud commented 5 years ago

Are you running k3v on the same machine you ran kubeadm on?

gokulpch commented 4 years ago

Yes, I am using the base-cluster created using Kubeadm