Troubleshooting

The DD agent startup failed on container as its not auto detecting container hostname. Agent works fine when its on a host , but when it runs on a container , we face this . Relook at the agent configuration to fix the issue Fix : The issue was due to Agent unable to connect […]

Jenkins Windows Installation

Warning DNSConfigForming kubelet Search line limits were exceeded, some search paths have been omitted, the applied search line is : xxx.svc.cluster.local cluster.local  This can be ignored and was ignored . It was just common to everything

Failed to verify ID token : failed to verify signature: fetching keys : get failed Get “https://xx.xxxxx.com/keys”: context deadline exceed while accessing https://abcxyz.com/ This issue was intermittent due to the new service account and its configuration . Rolled back to previous config and issue got fixed . Further debug required to find the root cause

For a specific cluster Datadog is reporting a change of Max, Min and Current Replicas about every 20 mins for the metric kubernetes_state.hpa.max_replicas . The actual number of pods/containers does not look to be changing neither the config files for the cluster. Rare cases – This could be a Datadog visualization thing. Using max by

Is there a suggested limit for setting the CPU and Memory resource limit for a pod Obviously yes . The resource request should be near where the application run 100% of the time . The intention is you will need to operate near the request setting, tolerate spikes above that and stay out of ‘gray

  Reason : One such scenario – During a node scale down activity, the POD scheduled on nodes being marked for scale down but failed to drain . After deleting the POD few times , it got scheduled on the stable node and the POD started properly with the volume mount  

Troubleshooting : – Checked the dedicated node having issues with docker – When checked docker seems healthy enough to be passing checks but not healthy enough to run pods – This scenario happens typically when underlying infra issue like I/O being exhausted but the node looked fine – After few mins , the PODs in Error

Getting the below error while trying to get default-quotas for bank-pl namespace Solution : quota and resourcequota will show the same thing luckily in kubernetes.  Run a command like this to get what you need . kubectl n=bank-pl get resourcequota -o yaml

Streaming movies, Web-series , sports has been the current market trend . Google ‘world cup streaming’ and you can find n number of streaming platforms . Considering the current market trend & customers expectation of flawless streaming, setting up the technology platform has become a challenge. We have multiple tools options to handle the workload

The DD agent startup failed on container as its not auto detecting container hostname. Agent works fine when its on a host , but when it runs on a container , we face this . Relook at the agent configuration to fix the issue Fix : The issue was due to Agent unable to connect

Kubernetes nodes use the container runtime to launch, manage, and stop containers running in Pods. The containerd runtime is an industry-standard container runtime that’s supported by GKE. The containerd runtime provides the layering abstraction that allows for the implementation of a rich set of features like gVisor and Image streaming to extend GKE functionality. The containerd runtime is considered more resource efficient and

Problem Statement Elastic Kubernetes Service (EKS) is predominantly used by many of the Organizations because it is an upstream and certified conformant version of Kubernetes with backported security fixes. It also provides a managed Kubernetes experience for performant, reliable and secure Kubernetes clusters. In a rapidly growing Business or Organization, where the Workloads deployed to

Issue: Datadog unable to post the Payload from the nodes provisioned by Karpenter. It prompts with the below error complaining about Multiple Mount points in your Kubernetes Pod. 2023–01–03 18:37:16 UTC | CORE | WARN | (pkg/collector/python/datadog_agent.go:125 in LogMessage) | disk:e5dffb8bef24336f | (disk.py:135) | Unable to get disk metrics for /host/var/run/containerd/io.containerd.runtime.v2.task/k8s.io/84b24aadc886673856bde8c5 ceb172658ec8e4f6d2d30e13b4c7ed2528da00af/rootfs/host/proc/sys/fs/binfmt_misc: [Errno 40] Too

Solution : è sudo su – è cd /etc/apt/sources.list.d è vi kubernetes.list deb http://apt.kubernetes.io/ kubernetes-xenial main è apt update è apt-get install -y kubelet kubeadm kubectl For more such technical blogs — visit us — cubensquare.com