kubeadm

How to connect to ingress remotely and use a Kubernetes application?

白昼怎懂夜的黑 提交于 2020-01-06 04:40:50
问题 I have an application running on kubernetes and I am using minikube for developing and testing it. I set up the minikube, ingress and application and they are working locally as I described here "Traefik ingress does not work with cluster IP" but I don't know how to connect to my application from a remote machine. What I want to do is, I want to run some performance test and find the bottleneck in my application. The application and minikube are located on machine-A and I want to send some

Configure AWS publicIP for a Master in Kubernetes

隐身守侯 提交于 2020-01-05 04:00:29
问题 I did create a Master Cluster with the following command: kubeadm init --pod-network-cidr $CALICO_NETWORK Now it is listening in the internal IP 10.3.8.23:6443, which is ok because I want that the master uses the internal IP to communicate with Nodes. Now I want to access the cluster using the public IP and I get the following error: http: proxy error: x509: certificate is valid for 10.96.0.1, 10.3.8.23, not for 18.230.*.*. How can I generate an additional certificate for the publicIP? I need

Can't see logs of kubernetes pod

╄→尐↘猪︶ㄣ 提交于 2020-01-05 03:33:09
问题 After installing kubernetes cluster following this guide I decided to check logs of system pod kube-scheduler to ensure that all works fine: kubectl logs --namespace kube-system kube-scheduler-user223225-pc but I got next error message: Error from server: Get https://10.2.2.131:10250/containerLogs/kube-system/kube-scheduler-user-pc/kube-scheduler: dial tcp 10.2.2.131:10250: getsockopt: no route to host I try to get logs from other pods and got the same error. I run the cluster on Ubuntu 16.04

Kubeadm init stops at image pulling

五迷三道 提交于 2020-01-03 04:38:06
问题 I'm having some troubles with initializing the master using kubeadm .. I'm trying to follow https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/ . I installed docker , kubelet , kubeadm and kubectl . Now I executed kubeadm init , but it stops at [init] This might take a minute or longer if the control plane images have to be pulled. I looked into journalctl and there I found out that: Unable to update cni config: No networks found in /etc/cni/net.d and Failed to list *v1.Pod:

ipvsadm not showing any entry in kubeadm cluster

Deadly 提交于 2020-01-02 08:37:09
问题 I have installed kubeadm and created service and pod: packet@test:~$ kubectl get pod NAME READY STATUS RESTARTS AGE udp-server-deployment-6f87f5c9-466ft 1/1 Running 0 5m udp-server-deployment-6f87f5c9-5j9rt 1/1 Running 0 5m udp-server-deployment-6f87f5c9-g9wrr 1/1 Running 0 5m udp-server-deployment-6f87f5c9-ntbkc 1/1 Running 0 5m udp-server-deployment-6f87f5c9-xlbjq 1/1 Running 0 5m packet@test:~$ kubectl get service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1

how to upgrade kubernetes from v1.10.0 to v1.10.11

戏子无情 提交于 2019-12-30 07:14:48
问题 i installed kubernetes via kubeadm under the 1.9 and upgraded it to 1.10.0 a while back using kubeadm upgrade . i'm quite happy with 1.10.x and don't want to deal with potential issues with upgrading to anything newer just yet. So i would like to upgrade to 1.10.11. i tried $ kubeadm upgrade plan v1.10.11 [preflight] Running pre-flight checks. [upgrade] Making sure the cluster is healthy: [upgrade/config] Making sure the configuration is correct: [upgrade/config] Reading configuration from

How to correctly recreate a kubeadm 1.15.0 cluster?

落花浮王杯 提交于 2019-12-24 05:45:32
问题 I've created a 1.15.0 single-node kubeadm on a fresh installed Ubuntu 18.04.2 LTS. Then I deleted the cluster and recreated it. But now I can't recreate it anymore (I get etcd preflight-check error): [init] Using Kubernetes version: v1.15.0 [preflight] Running pre-flight checks [WARNING IsDockerSystemdCheck]: detected "cgroupfs" as the Docker cgroup driver. The recommended driver is "systemd". Please follow the guide at https://kubernetes.io/docs/setup/cri/ error execution phase preflight:

Container runtime network not ready: cni config uninitialized

做~自己de王妃 提交于 2019-12-23 06:59:12
问题 I'm installing kubernetes(kubeadm) on centos VM running inside Virtualbox , so with yum I installed kubeadm, kubelet and docker . Now while trying to setup cluster with kubeadm init --pod-network-cidr=192.168.56.0/24 --apiserver-advertise-address=192.168.56.33/32 i run into the following error : Unable to update cni config: No networks found in /etc/cni/net.d Container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni

kubectl not able to pull the image from private repository

牧云@^-^@ 提交于 2019-12-20 09:39:48
问题 I am running kubeadm alpha version to set up my kubernates cluster. From kubernates , I am trying to pull docker images which is hosted in nexus repository. When ever I am trying to create a pods , It is giving "ImagePullBackOff" every time. Can anybody help me on this ? Detail for this are present in https://github.com/kubernetes/kubernetes/issues/41536 Pod definition : apiVersion: v1 kind: Pod metadata: name: test-pod labels: name: test spec: containers: - image: 123.456.789.0:9595/test

User “system:anonymous” cannot get path “/”

假装没事ソ 提交于 2019-12-14 00:30:35
问题 I just setup a kubenetes cluster base on this link https://kubernetes.io/docs/setup/independent/create-cluster-kubeadm/#multi-platform I check with kubectl get nodes, then the master node is Ready, but when I access to the link https://k8s-master-ip:6443/ it show the error: User "system:anonymous" cannot get path "/". What is the trick I am missing ? 回答1: The latest kubernetes deployment tools enable RBAC on the cluster. Jenkins is relegated to the catch-all user system:anonymous when it