thakurvaibhav/k8s

Important production-grade Kubernetes Ops Services

k8s's Issues

node-exporter pod running failed on EKS

Logs: 0/3 nodes are available: 2 node(s) didn't match node selector, 3 node(s) didn't have free ports for the requested pod ports.

Error: opening storage failed: create dir: mkdir /prometheus/wal: permission denied

Hello,
Firstly, thank you for sharing these resources.
When I deploy prometheus kubectl apply -f k8s/monitoring/prometheus the container fails to launch successfully. The logs show following error.
level=error caller=main.go:688 err="opening storage failed: create dir: mkdir /prometheus/wal: permission denied"

I refered to Issue 12176 on Helm charts.

Fixed the issue by updating the prometheus-deployment.yaml as below

...
securityContext:
        fsGroup: 0
        runAsNonRoot: false
        runAsUser: 0
...

Getting error when Deploying Alertmananger

I'm trying to deploy the Alertmanager onto a AWS EKS cluster, and it's erroring. When I look at the logs, I get the following:

level=error ts=2020-05-26T20:50:56.287Z caller=coordinator.go:124 component=configuration msg="Loading configuration file failed" file=/etc/alertmanager/config.yml err="unsupported scheme "" for URL"

Any ideas why this is happening?

Kubernetes deployment metrics calculate is wrong

I have two deployments foo-api and foo-api-stg, when aggregating data from foo-api metrics from foo-api-stg are summed together. This is because of the regex used in the dashboard:

sum (container_memory_working_set_bytes{image!="",name=~"^k8s_.*",pod_name=~"^$Deployment.*$",container_name!="POD"}) by (pod_name)

Anyway thoughts on how truly separate the pod metrics?

Can't get metrics of PersistentVolumeClaim

I need collect below metrics, Pls help me !

• kubelet_volume_stats_available_bytes

• kubelet_volume_stats_capacity_bytes

• kubelet_volume_stats_inodes

• kubelet_volume_stats_inodes_free

• kubelet_volume_stats_inodes_used

• kubelet_volume_stats_used_bytes