kubernetes-cluster

How to route test traffic through kubernetes cluster (minikube)?

生来就可爱ヽ(ⅴ<●) 提交于 2021-02-11 04:33:10
问题 I have a minikube cluster with two pods (with ubuntu containers). What I need to do is route test traffic from one port to another through this minikube cluster. This traffic should be sent through these two pods like in the picture. I am a beginner in this Kubernetes stuff so I really don't know how to do this and which way to go... Please, help me or give me some hints. I am working on ubuntu server ver. 18.04. enter image description here 回答1: I agree with an answer provided by @Harsh

What is the difference between current and available pod replicas in kubernetes deployment?

那年仲夏 提交于 2021-02-07 07:59:34
问题 I am trying to get my hands dirty on Kubernetes. I am firing following command: kubectl get deployment and I get the following headers in the output: I can't find the difference between current and available columns in the following output? I know that official documentation gives a small description each of these fields, but it doesn't answer my following questions: Is Current <= Desired true? Is Up-to-Date <= Current true? Is Up-to-Date > Current and Up-to-Date <= Desired true? Is Available

What is the difference between current and available pod replicas in kubernetes deployment?

对着背影说爱祢 提交于 2021-02-07 07:59:31
问题 I am trying to get my hands dirty on Kubernetes. I am firing following command: kubectl get deployment and I get the following headers in the output: I can't find the difference between current and available columns in the following output? I know that official documentation gives a small description each of these fields, but it doesn't answer my following questions: Is Current <= Desired true? Is Up-to-Date <= Current true? Is Up-to-Date > Current and Up-to-Date <= Desired true? Is Available

GCLOUD Kubernetes in f1-micro results in (Node pools of f1-micro machines are not supported due to insufficient memory)

╄→尐↘猪︶ㄣ 提交于 2020-04-30 06:25:42
问题 I tried to start a new f1-micro node in my cluster using Googles UI and it silently fails. So I decided to run it using gcloud to see if that one provides more details And so I ran the following gcloud container node-pools create my-f1-pool --image-type ubuntu --machine-type=f1-micro --cluster bcomm-sg-cluster --disk-size=10GB --enable-autoscaling --min-nodes=2 --max-nodes=6 --zone=asia-southeast1-a --enable-autorepair This is the result I got instead WARNING: Modifications on the boot disks

Digital ocean kubernetes cluster connection error

早过忘川 提交于 2019-12-31 05:07:57
问题 I have created kubernetes cluster on digital ocean having 1 worker node and one master node. As per digital ocean guide line i followed step and download kubernetes cluster config file kubectl --kubeconfig="filename.yaml" get nodes but it is showing Unable to connect to the server: unexpected EOF While Kubernetes cluster is Up and Running 回答1: Please make sure you are using right config yaml file otherwise try to destroy and create fresh Kubernetes cluster on Digital Ocean and try again. It

How to find master node from worker node in Kubernetes

给你一囗甜甜゛ 提交于 2019-12-06 11:05:53
问题 I need to know to which master node my current worker node is connected. I can see the worker nodes by typing "kubectl get nodes" command in the master node, but I need to find the master node from the worker node itself. In simple words, How to find the master node from the worker node in the kubernetes cluster? 回答1: You can usually find it on your kubelet config file: /etc/kubernetes/kubelet.conf $ cat /etc/kubernetes/kubelet.conf apiVersion: v1 clusters: - cluster: certificate-authority

How to find master node from worker node in Kubernetes

大城市里の小女人 提交于 2019-12-04 17:41:26
I need to know to which master node my current worker node is connected. I can see the worker nodes by typing "kubectl get nodes" command in the master node, but I need to find the master node from the worker node itself. In simple words, How to find the master node from the worker node in the kubernetes cluster? You can usually find it on your kubelet config file: /etc/kubernetes/kubelet.conf $ cat /etc/kubernetes/kubelet.conf apiVersion: v1 clusters: - cluster: certificate-authority-data: REDACTED server: https://1.1.1.1:6443 <== here name: default-cluster contexts: - context: cluster:

Digital ocean kubernetes cluster connection error

爱⌒轻易说出口 提交于 2019-12-02 09:33:14
I have created kubernetes cluster on digital ocean having 1 worker node and one master node. As per digital ocean guide line i followed step and download kubernetes cluster config file kubectl --kubeconfig="filename.yaml" get nodes but it is showing Unable to connect to the server: unexpected EOF While Kubernetes cluster is Up and Running Please make sure you are using right config yaml file otherwise try to destroy and create fresh Kubernetes cluster on Digital Ocean and try again. It should work properly In my case i have blinding fire cluster more thn 10-11 time with different configuration