Max Williams comments

Results 95 comments of


                                            Max Williams

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

Same for `v1.6.3` 😐

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

Makes sense but why wasn't this a problem with `v1.5.x` releases? Or is it related to moving to EKS/AMI `1.16`?

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

But there's no changes to that file between the `v1.6.2` and `v1.6.3` releases? https://github.com/aws/amazon-vpc-cni-k8s/commits/master/config/v1.6/aws-k8s-cni.yaml

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

Any update @mogren?

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

So two suggestions now: 1. kube-proxy should have `readOnlyRootFilesystem: false` 2. Downgrade kube-proxy to `kube-proxy:v1.16.12` Any confirmation from AWS about the issue and resolution?

EKS 1.16 / v1.6.x: "couldn't get current server API group list; will keep using cached value"

> Could you please provide the kube-proxy configs that you have where this issue shows up? It's default EKS > Is this on EKS clusters? Yes > What Kubernetes version?...

[pg-repack-scheduler] Keep Looping

@allenheydari2019 what chart are you talking about? there's over 40 charts in this repo...

[pg-repack-scheduler] Keep Looping

Perhaps @Naginder-Singh can help you 🙂

[pg-repack-scheduler] Keep Looping

@allenheydari2019 all the code is in the chart, including the dockerfile and scripts. You are welcome to debug it yourself and creating a PR.

[node-problem-detector] Should mount /dev/kmsg by default

PRs welcome 🙂