heapster


Autoscaling (HPA) failed to get CPU consumption: cannot unmarshal object into Go value of type []v1alpha1.PodMetrics

耗尽温柔 提交于 2020-01-07 02:24:10
问题 I am trying to test the HPA (horizontal pod autoscaling) in my Kubernetes cluster. Heapster is up and running and I think it works well since I'm able to see metrics in Grafana. Also the DNS addon is working perfectly. Looking inside the HPA I can see the error "failed to get CPU consumption and request: failed to unmarshall heapster response: json: cannot unmarshal object into Go value of type []v1alpha1.PodMetrics" $ kubectl describe hpa php-apache Name: php-apache Namespace: default Labels

Kubernetes : configuring custom influxdb sink for heapster running in kube-system namespace on GKE

假装没事ソ 提交于 2019-12-13 13:24:21
问题 I need to configure heapster to send kubernetes cluster metrics to our custom influx db server . For this I tried to edit heapster deployment in kube-system namespace but after some time deployment is getting reverted to original state . I am using GKE , master version is 1.5.7 and node version is 1.5.6 . 回答1: As for now, a custom configuration of addons is not supported on GKE. Any changes to the default Heapster configuration will be reverted by addon-manager. If the default Heapster

Provide authentication for heapster to connect to secured kube API server in GKE

房东的猫 提交于 2019-12-12 06:16:53
问题 I am trying to deploy heapster in a cluster and collect metrics and store it in Influxdb . I can provide sink for Influxdb . But I am not sure how to provide the value for --source flag to connect to the secured kube API server . Can someone help me to find out this. Note: I am trying to deploy heapster in the same cluster where the kube API server is running. Thanks in advance. 回答1: I use heapster with parameter --source=kubernetes:http://kubernetes.default?inClusterConfig=false&insecure

Stackdriver custom metric aggregate alerts

为君一笑 提交于 2019-12-08 03:59:44
问题 I'm using Kubernetes on Google Compute Engine and Stackdriver. The Kubernetes metrics show up in Stackdriver as custom metrics. I successfully set up a dashboard with charts that show a few custom metrics such as "node cpu reservation". I can even set up an aggregate mean of all node cpu reservations to see if my total Kubernetes cluster CPU reservation is getting too high. See screenshot. My problem is, I can't seem to set up an alert on the mean of a custom metric. I can set up an alert on

Running kubernetes autoscalar

北城余情 提交于 2019-12-04 04:31:41
问题 I have a replication controller running with the following spec: apiVersion: v1 kind: ReplicationController metadata: name: owncloud-controller spec: replicas: 1 selector: app: owncloud template: metadata: labels: app: owncloud spec: containers: - name: owncloud image: adimania/owncloud9-centos7 ports: - containerPort: 80 volumeMounts: - name: userdata mountPath: /var/www/html/owncloud/data resources: requests: cpu: 400m volumes: - name: userdata hostPath: path: /opt/data Now I run a hpa

Running kubernetes autoscalar

不羁的心 提交于 2019-12-01 21:14:17
I have a replication controller running with the following spec: apiVersion: v1 kind: ReplicationController metadata: name: owncloud-controller spec: replicas: 1 selector: app: owncloud template: metadata: labels: app: owncloud spec: containers: - name: owncloud image: adimania/owncloud9-centos7 ports: - containerPort: 80 volumeMounts: - name: userdata mountPath: /var/www/html/owncloud/data resources: requests: cpu: 400m volumes: - name: userdata hostPath: path: /opt/data Now I run a hpa using autoscale command. $ kubectl autoscale rc owncloud-controller --max=5 --cpu-percent=10 I have also

How to get the resource usage of a pod in Kubernetes?

纵然是瞬间 提交于 2019-11-30 04:09:12
问题 How can we get the real resource usage (not resource requests) of each pod on Kubernetes by command line? Heapster is deprecated. Meanwhile, Metrics-server still does not support kubectl top pod . Heapster - I deployed Heapster using the following command $ heapster/deploy/kube.sh start kubectl get pods --all-namespaces NAMESPACE NAME READY STATUS RESTARTS AGE kube-system calico-node-hlcbl 2/2 Running 0 39m kube-system calico-node-m8jl2 2/2 Running 0 35m kube-system coredns-78fcdf6894-bl94w 1

工具导航Map