Open NimJay opened 3 weeks ago
For now, I've manually deleted those namespaces (for which pull-requests have been closed/merged):
kubectl delete namespace pr2644
kubectl delete namespace pr2652
kubectl delete namespace pr2609
kubectl delete namespace pr2637
kubectl delete namespace pr2638
kubectl delete namespace pr2664
kubectl delete namespace pr2661
kubectl delete namespace pr2651
kubectl delete namespace pr2639
kubectl delete namespace pr2666
kubectl delete namespace pr2684
kubectl delete namespace pr2649
kubectl delete namespace pr2640
kubectl delete namespace pr2663
kubectl delete namespace pr2662
kubectl delete namespace pr2667
kubectl delete namespace pr2641
kubectl delete namespace pr2655
kubectl delete namespace pr2643
Looking into root cause now.
cleanup.yaml
from running automatically.The screenshot above is for this run/invocation of the cleanup.yaml workflow. I will click "Approve and run" now. Update: I clicked "Approve and run" but the workflow failed because I had already manually cleaned up the namespace — see my previous comment. All good.
CC: @bourgeoisor, just FYI. :) For now, whenever we merge (or close) a pull-request, we may need to manually "Approve an run" the cleanup.yaml workflow. See list of cleanup.yaml workflows "runs" (invocations) here.
Oh wow good catch!-- And extremely annoying.
prs-gke-cluster
.prs-gke-cluster
)'s CPU and memory: