ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
I am trying to debug a pod with the status "ImagePullBackOff". The pod is in the namespace minio-operator, but when I try to to describe the pod, it is apparently not found. Why does that happen? [psr-admin@zon-psr-2-u001 ~]$ kubectl get all -n minio-operator NAME READY STATUS RESTARTS AGE pod/minio-operator-5dd99dd858-n6fdj 0/1 ImagepullBackoff 0 7d NAME RE
Asked · 07 Feb 2023, 10:02 UTC
answered · 10 Feb 2023, 10:02 UTC
To exec into a container in a pod, I use the following two commands (note the template flag in the first command trims the output to print just the name of the pods): $ kubectl get pods --template '{{range .items}}{{.metadata.name}}{{"\n"}}{{end}}' app-api-6421cdf4fd-x9tbk app-worker-432f86f54-fknxw app-frontend-87dd65d49c-6b4mn app-rabbit-413632c874-s2ptw $
I need to monitor my container memory usage running on kubernetes cluster. After read some articles there're two recommendations: container_memory_rss , container_memory_working_set_bytes The definitions of both metrics are said (from the cAdvisor code) container_memory_rss : The amount of anonymous and swap cache memory container_memory_working_set_bytes :
How is container port different from targetports in a container in Kubernetes? Are they used interchangeably, if so why? I came across the below code snippet where containerPort is used to denote the port on a pod in Kubernetes. apiVersion: apps/v1 kind: Deployment metadata: name: postgres-deployment labels: app: demo-voting-app spec: replicas: 1 selector: m
I have tried to run Helm for the first time. I am having deployment.yaml, service.yaml and ingress.yaml files alongwith values.yaml and chart.yaml. deployment.yaml apiVersion: apps/v1 kind: Deployment metadata: name: abc namespace: xyz labels: app: abc app.kubernetes.io/managed-by: {{ .Release.Service }} spec: replicas: 3 template: spec: containers: - name:
Trying to figure out how to expose multiple TCP/UDP services using a single LoadBalancer on Kubernetes. Let's say the services are ftpsrv1.com and ftpsrv2.com each serving at port 21. Here are the options that I can think of and their limitations : One LB per svc: too expensive. Nodeport : Want to use a port outside the 30000-32767 range. K8s Ingress : does
The goal is to understand whether Kubernetes retains container logs for a pod that has exited due to a CrashLoopBackOff event after the pod itself is deleted or evicted. Currently, logs are stored only on the node’s filesystem and are removed according to the node’s log‑rotation policy, with no built‑in API to access them once the pod is gone. This leaves an
We created a kubernetes cluster for a customer about one year ago with two environments; staging and production separated in namespaces. We are currently developing the next version of the application and need an environment for this development work, so we've created a beta environment in its own namespace. This is a bare metal kubernetes cluster with Metal
I am creating an InfluxDB deployment in a Kubernetes cluster (v1.15.2), this is my yaml file: apiVersion: extensions/v1beta1 kind: Deployment metadata: name: monitoring-influxdb namespace: kube-system spec: replicas: 1 template: metadata: labels: task: monitoring k8s-app: influxdb spec: containers: - name: influxdb image: registry.cn-hangzhou.aliyuncs.com/go