Tatiana Krishtop

/remove-lifecycle stale

I used an example from the [kubernetes docs](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#exceed-a-container-s-memory-limit) to exceed a container's memory limit, ran it both on `minikube` and on `kind`, and reproduced the issue. While `minikube` shows OOMKilled...

> @tkrishtop which driver are you using with minikube? VM or docker? @BenTheElder kvm2, sorry, I forgot to put it, got the logs updated now.

minikube on driver=podman results in Error/CrashLoopBackOff (not in OOMKilled as minikube on kvm2): ``` $ minikube start --driver=podman 😄 minikube v1.25.2 on Fedora 36 ✨ Using the podman driver based...

Hi @joemilacek I believe that the results displayed by `kubectl top nodes` are correct: - allocatable memory: 1209608Ki = 1181Mi - memory usage: 2899Mi --> 2899 / 1181 = 245%...

I'd like to add an update on why kubectl shows that memory usage is larger than 100% and how to fix that. ## Why is the percentage larger than 100%...

Hi @mikelo! > I wanted to deliberately create a pod that would go "out of memory" I used a classical example from the [kubernetes docs](https://kubernetes.io/docs/tasks/configure-pod-container/assign-memory-resource/#exceed-a-container-s-memory-limit), ran it both on minikube...

Hello team, that's an old issue but we keep seeing it regularly while running Preflight [which currently runs operator-sdk 1.22.2](https://github.com/redhat-openshift-ecosystem/openshift-preflight/blob/main/Dockerfile#L46). Here are the logs from preflight.log (BasicSpecCheck.json is not created...

Upd. In half of such situations, the scorecard-test pod is stuck in the namespace, failing to terminate. This last bad thing should be easy to fix, whatever the reason for...

/remove-lifecycle stale