profile
viewpoint

Ask questionsProtokube has sustained cpu usage above 100%

1. What kops version are you running? The command kops version, will display this information. 1.11.0

2. What Kubernetes version are you running? kubectl version will print the version if a cluster is running or provide the Kubernetes version specified as a kops flag. v1.11.7

3. What cloud provider are you using? aws

4. What commands did you run? What is the simplest way to reproduce this issue?

We're running top on the node and protokube is consistently bursting over 100%

Are there any leads to what could be causing high cpu usage? I'm not sure what else to report this since we're not running any kops commands.

kubernetes/kops

Answer questions sheldonkwok

We figured out it was due to having hundreds of nodes with the protokube mesh. Switching to dns based discovery solved. Had to create a new cluster though.

useful!

Related questions

Unable to use a local filesystem state store hot 2
Kops 1.12-beta.2 won't/can't bring up etcd server, manager or kube-api hot 1
kube controller manager refuses to connect after upgrading from 1.10.6 to 1.11.7 hot 1
Missing kops controller support for cloudproviders hot 1
InstanceGroup not found (for etcd ap-southeast-2a/main): "ap-southeast-2a" hot 1
Rolling-update fails due to calico-node with 1.12.0-beta.2 hot 1
Kubelet Unable To Apply Reserved Cgroup Limits because Cgroup does not exist hot 1
etcd3 and kube-apiserver fail on terraform apply after terraform destroying w/ kops generated config hot 1
Upgrade from Kops 1.11 to 1.12 has failed. hot 1
Couldn't find key etcd_endpoints in ConfigMap kube-system/calico-config hot 1
Allow just one instance type in mixedInstancesPolicy hot 1
kubectl command: Unable to connect to the server: EOF hot 1
DNS record for public API address not updated hot 1
etcd3 and kube-apiserver fail on terraform apply after terraform destroying w/ kops generated config hot 1
Issues encountered deploying to OpenStack hot 1
source:https://uonfu.com/
Github User Rank List