kubeadm

kubeadm: master node never ready

随声附和 提交于 2019-12-10 13:13:41
问题 I'm following a blog post to setup a kubernetes cluster with kubeadm. So I have a Virtualbox created with bridge network and simply followed the instructions. I initially just did kubeadm init and it didn't work (master NotReady). So I figured maybe an older version might work better. So I did kubeadm init --kubernetes-version v1.6.2 It finished quite quickly. But kubeadm get nodes always returns: master NotReady 4m v1.6.3 I checked the docker images that was downloaded and they're like this:

Assign External IP to a Kubernetes Service

非 Y 不嫁゛ 提交于 2019-12-10 01:01:07
问题 EDIT: The whole point of my setup is to achieve (if possible) the following : I have multiple k8s nodes When I contact an IP address (from my company's network), it should be routed to one of my container/pod/service/whatever. I should be able to easily setup that IP (like in my service .yml definition) I'm running a small Kubernetes cluster (built with kubeadm) in order to evaluate if I can move my Docker (old)Swarm setup to k8s. The feature I absolutely need is the ability to assign IP to

kubernetes v1.7.1 kubeadm join hostname “” could not be reached error

假如想象 提交于 2019-12-08 21:39:52
问题 Today I recreated my cluster with v1.7.1 when I run the kubeadm join --token 189518.c21306e71082d6ec command, it giving the below error. this used work in previous version of kubernetes. Is something changed in this version, How do we resolve this? [root@k8s17-02 ~]# kubeadm join --token 189518.c21306e71082d6ec 192.168.15.91:6443 [kubeadm] WARNING: kubeadm is in beta, please do not use it for production clusters. [preflight] Running pre-flight checks [preflight] WARNING: hostname "" could not

Kubernetes dashboard showing Unauthorized

纵饮孤独 提交于 2019-12-08 08:53:51
问题 I configured kubernetes cluster with one master and 4 worker nodes using KUBEADM tool IN LOCAL. All nodes are running fine. deployed an app and able access that app from browser. I have tried many ways to create a dashboard using kubectl but i am failed. TRY1: tried directly with the below command: $ sudo kubectl proxy --address="172.20.22.101" -p 8001 tried to access the dashboard using the url http://172.20.22.101:8001/api/v1, but it is saying unauthorized. TRY2: created dashboard-admin

How to troubleshoot metrics-server on kubeadm?

雨燕双飞 提交于 2019-12-08 06:51:33
问题 I have a working 1.15.1 kubenetes cluster using kubeadm on bare-metal and just deployed metrics-server as in the docs: git clone https://github.com/kubernetes-incubator/metrics-server.git kubectl create -f metrics-server/deploy/1.8+/ After some time I try kubectl top node and I get as response: error: metrics not available yet Also when I try kubectl top pods I get: W0721 20:01:31.786615 21232 top_pod.go:266] Metrics not available for pod default/pod-deployment-57b99df6b4-khh84, age: 27h31m59

kubectl - error: You must be logged in to the server

烈酒焚心 提交于 2019-12-08 02:27:29
问题 I have configured OIDC with k8s installed using kubeadm. After the configuration, when I run the command kubectl --user=name@gmail.com get nodes I get error: You must be logged in to the server (the server has asked for the client to provide credentials (get nodes)) Can someone please help me with this? 回答1: I use kubectl --username=name@gmail.com get nodes and it works. Earlier I was using the parameter --user instead of --username . 回答2: Your password is probably missing. 来源: https:/

Is there a best practice to reboot a cluster

徘徊边缘 提交于 2019-12-08 00:51:36
问题 I followed Alex Ellis' excellent tutorial that uses kubeadm to spin-up a K8s cluster on Raspberry Pis. It's unclear to me what the best practice is when I wish to power-cycle the Pis. I suspect sudo systemctl reboot is going to result in problems. I'd prefer not to delete and recreate the cluster each time starting with kubeadm reset . Is there a way that I can shutdown and restart the machines without deleting the cluster? Thanks! 来源: https://stackoverflow.com/questions/48362855/is-there-a

Kubernetes WatchConnectionManager: Exec Failure: HTTP 403

纵然是瞬间 提交于 2019-12-07 18:51:57
问题 I'm experiencing Error Expected HTTP 101 response but was '403 Forbidden' After I setup a new Kubernetes cluster using Kubeadm with a single master and two workers, as I submit a pyspark sample app I encountered below ERROR message: spark-submit command spark-submit --master k8s://master-host:port \ --deploy-mode cluster --name test-pyspark \ --conf spark.kubernetes.container.image=mm45/pyspark-k8s-example:2.4.1 \ --conf spark.kubernetes.pyspark.pythonVersion=3 \ --conf spark.executor

K8s Dashboard not logging in (k8s version 1.11)

浪尽此生 提交于 2019-12-07 08:00:27
问题 I did K8s(1.11) cluster using kubeadm tool. It 1 master and one node in the cluster. I applied dashboard UI there. kubectl create -f https://raw.githubusercontent.com/kubernetes/dashboard/master/src/deploy/recommended/kubernetes-dashboard.yaml Created service account (followed this link: https://github.com/kubernetes/dashboard/wiki/Creating-sample-user) apiVersion: v1 kind: ServiceAccount metadata: name: admin-user namespace: kube-system and apiVersion: rbac.authorization.k8s.io/v1beta1 kind:

How to use kubeadm upgrade to change some features in kubeadm-config

本小妞迷上赌 提交于 2019-12-07 06:24:13
问题 I want to install kube-prometheus on my existing kubernetes cluster(v1.10). Before that, the doc says I need to change the ip address of contrller/scheduler from 127.0.0.1 to 0.0.0.0 . And it also recommand to use kubeadm config upgrade to change these features: controllerManagerExtraArgs: address: 0.0.0.0 schedulerExtraArgs: address: 0.0.0.0 After reading the doc, i tried with the below command, but it didn't work: kubeadm upgrade --feature-gates controllerManagerExtraArgs.address=0.0.0.0 I