Matti Paksula
Matti Paksula
>Notice how the command line appears to freeze after pulling and starting the container. is not true anymore
we use loopback 3 because it's a declarative way to build an API with the loopback json - with next/4 it's no longer supported. I'm having hard time seeing what's...
cpu usage NaN, cores: 0 - but memory works prometheus installed with helm chart values: https://github.com/matti/eksler/blob/9fbd98e79233912bd46489a6104ff869256f1558/helm/prometheus-1/values.yml AWS EKS 1.22 ipv6 with eksctl
**Describe the bug** webview crashes or something for one cluster, see video https://user-images.githubusercontent.com/3893/174637924-3d581fb5-cfa6-4f04-bd03-eb6b5d580b29.mp4 **To Reproduce** Leave lens running, shutdown laptop, drink beer, open laptop the next day. Repeat until success....
``` git clone https://github.com/matti/kung cd kung ./test ``` https://user-images.githubusercontent.com/3893/167472594-aac842b8-fbde-4da4-a86b-796f1fa0d41f.mp4
 maybe with an option, but also as default behaviour would be okay - nobody needs to see these.
Currently lens shows node cpu/mem like this: These same cpu/mem should be shown in the pod listing as well like infra.app does:
1. add cluster `$HOME/.kube/test` 2. connect to it, pin it to "hot bar", do lenssing 3. re-create the cluster (CA changes etc) 4. overwrite `$HOME/.kube/test` 5. lens goes nuts
cluster-autoscaler can not scale an (otherwise) empty node down: ``` Fast evaluation: node ip-192-168-25-147.eu-north-1.compute.internal cannot be removed: non-daemonset, non-mirrored, non-pdb-assigned kube-system pod present: coredns-5bf7669654-l46wf ``` creating a PDB like this:...
for example #29