Skip to content

Commit

Permalink
Update addon-manager to v9.0.2, disable master negotiation and increa…
Browse files Browse the repository at this point in the history 
…se reconcile frequency
  • Loading branch information
@tstromberg
tstromberg committed Sep 19, 2019
1 parent 43a0d03 commit bdd2c75
Showing 1 changed file with 6 additions and 2 deletions.
8 changes: 6 additions & 2 deletions deploy/addons/addon-manager.yaml.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -19,16 +19,20 @@ metadata:
namespace: kube-system
labels:
component: kube-addon-manager
version: v9.0
version: v9.0.2
kubernetes.io/minikube-addons: addon-manager
spec:
hostNetwork: true
containers:
- name: kube-addon-manager
image: {{default "k8s.gcr.io" .ImageRepository}}/kube-addon-manager{{.ExoticArch}}:v9.0
image: {{default "k8s.gcr.io" .ImageRepository}}/kube-addon-manager{{.ExoticArch}}:v9.0.2
env:
- name: KUBECONFIG
value: /var/lib/minikube/kubeconfig
- name: TEST_ADDON_CHECK_INTERVAL_SEC
value: "5"

This comment has been minimized.

Sign in to view

Copy link
@mtreuberg

mtreuberg Jan 21, 2020 •
edited
Loading

@tstromberg
What was the reason to set this value to "5"?
It seems that the kube-addon-manager-minikube uses quite a lot of CPU, following this comment (#3207 (comment)), changing the value to "60" reduces the CPU usage, seen by kubectl top pod -A.

For example, with a value of "5" the kube-addon-manager-minikube pod uses about as much CPU as all other Pods combined in my local cluster and that seems a bit odd to me.

Any thoughts? Thanks
- name: ADDON_MANAGER_LEADER_ELECTION
value: "false"
imagePullPolicy: IfNotPresent
resources:
requests:
Expand Down

0 comments on commit bdd2c75

Please sign in to comment.