Dušan Šušić
Dušan Šušić
@kishorj logs are sent to given mail. Thanks!
It just happened again @M00nF1sh @kishorj. Described one of the pods and caught this: ``` status: conditions: - lastProbeTime: null lastTransitionTime: "2022-08-15T10:55:29Z" status: "True" type: Initialized - lastProbeTime: null lastTransitionTime:...
It seems we are hitting the same issue as it is described in https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1205
@kishorj anything new here? Did you have any chance to take a look at the logs?
- clone repo - install nix - execute: nix-shell - stack setup - vim ~/.stack/config.yaml add: ``` nix: enable: true ``` - export TMPDIR=/tmp - ./scripts/build/cardano-sl.sh
@jpculp Running multiple EKS clusters with managed node groups with BottlerocketOS AMI. Each node has `arn:aws:iam::aws:policy/AmazonSSMManagedInstanceCore` policy attached. And it just worked with v1.6.2 and all previous versions, AWS Inspector...
@bcressey good to hear that support is coming! Thanks!
@kdaula is this supported now for BottlerocketOS 1.9.2 or 1.10.0 which isn't released yet? In Inspector console BottlerocketOS 1.9.2 is still listed as unsupported OS.
Understood. Control container is running and SSM agent is started, all instances have necessary roles. Still, instances are shown as ones with Unsupported OS. Running v1.9.2.
@arnaldo2792 it seems it started to scan instances with more than 2 days of delay, ami id: `ami-0e9e6e36c48fb0e8a` (us-east-2 region). Just to be sure, on v1.9.2 there's no single vulnerability...