ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #kubernetes
Feature state: Beta since Kubernetes v1.37; disabled by default More information about this feature To use this feature, you (or a cluster administrator) will need to enable the PodLevelResourceManagers feature gate for all relevant components in your cluster. See Enable Or Disable Feature Gates for
Started · 07 May 2022, 04:49 UTC
I am currently using the following to attempt to spread Kubernetes pods in a given deployment across all Kubernetes nodes evenly: spec: affinity: podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - weight: 100 podAffinityTerm: topologyKey: kubernetes.io/hostname labelSelector: matchExpressions: - key: app operator: In values: - api However, I
We have an AKS cluster and sometimes we end up with an issue where a deployment needs a restart (e.g. cached data has been updated and we want to refresh it or there is corrupt cache data we want to refresh). I've been using the approach of scaling the deployment to 0 and then scaling it back up using the commands below: kubectl scale deployments/<deploym
I understand that services use a selector to identify which pods to route traffic to by thier labels. apiVersion: v1 kind: Service metadata: name: svc spec: ports: - name: tcp protocol: TCP port: 443 targetPort: 443 selector: app: nginx Thats all well and good. Now what is the difference between this selector and the one of the spec.selector from the deploym
Whenever I am trying to run the docker images, it is exiting in immediately. CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES ae327a2bdba3 k8s-for-beginners:v0.0.1 "/k8s-for-beginners" 11 seconds ago Exited (1) 10 seconds ago focused_booth As per Container Logs standard_init_linux.go:228: exec user process caused: no such file or directory I have create
I'm trying to deploy a single web application to Minikube on my Mac, and then access it in the browser. I'm trying to use the simplest of setups, but it's not working, I just get a "connection refused" error and I can't figure out why. This is what I'm trying: $ minikube start --insecure-registry=docker.example.com:5000 😄 minikube v1.12.3 on Darwin 10.14.6 ✨
This page describes how to observe the status and health of resources that are dynamically allocated with DRA. Observability of dynamic resources You can check the status of dynamically allocated resources by using any of the following methods: kubelet device metrics ResourceClaim status Device heal
Feature state: Stable since Kubernetes v1.20 Kubernetes allow you to limit the number of process IDs (PIDs) that a Pod can use. You can also reserve a number of allocatable PIDs for each node for use by the operating system and daemons (rather than by Pods). Process IDs (PIDs) are a fundamental reso
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
docker