Robert-Stam
Robert-Stam
We see his behaviour here as well (on AWS) any news? I see the issue is set the closed, however it doesn't seems to be resolved?
> Hey @Robert-Stam Can you confirm which `aws.values.xxx.yaml` you have used in the deployment and which version of EKS you are using. It's likely that the version of crio is...
@No9 Hi Anton, any update on this?
I tested with k8s v1.29 on AKS (Azure) and GKE (Google), and it all resolves to 'unknown' as namespace. This is the output from the composer log on AKS ```...
@No9 I tried to create a small PR to update the packages and crictr version, however without luck. FYI, here is my PR: https://github.com/IBM/core-dump-handler/pull/158 Do you have tried k8s v1.29...
> crictl is already on the host on IKS and others so it isn't a useful test. > > Did you look for the compose logs as per this comment?...
> Do you have tried k8s v1.29 in the IBM cloud successfully? Do you have tried k8s v1.29 in the IBM cloud successfully?
> Sorry I missed your log output post for some reason. So it appears as though this command is executing but not returning a list of pods: > > ```...
@No9 Anton, I executed your command in the running container (ibm/core-dump-handler:v8.10.0) on AWS (with k8s v1.29). This is the result ``` [root@core-dump-lgd5p app]# ./crictl pods --name ip-10-87-16-57.eu-west-2.compute.internal -o json WARN[0000]...