Jeff Bunagan

Tested also on AKS and seeing the same problem: ``` $ k logs loggregator-bridge-59f5cb64bc-9scbb -n kubecf {"level":"info","ts":1615563276.4147344,"caller":"kubeconfig/getter.go:53","msg":"Using in-cluster kube config"} {"level":"info","ts":1615563276.414798,"caller":"kubeconfig/checker.go:36","msg":"Checking kube config"} Received non-pod object in watcher channel Error:...

I've turned on `DEBUG` logging for loggregator-bridge and this is the error I'm seeing: ``` Starting Loggregator {"level":"info","ts":1615410279.0113866,"caller":"kubeconfig/getter.go:53","msg":"Using in-cluster kube config"} {"level":"info","ts":1615410279.0114636,"caller":"kubeconfig/checker.go:36","msg":"Checking kube config"} Received event: {ERROR &Status{ListMeta:ListMeta{SelfLink:,ResourceVersion:,Continue:,RemainingItemCount:nil,},Status:Failure,Message:too old resource...

@mudler loggregator-bridge is using eirinix v0.3.1 https://github.com/cloudfoundry-incubator/eirini-loggregator-bridge/blob/master/go.mod#L4 so I'm assuming that it's got the fix you've mentioned since https://github.com/cloudfoundry-incubator/eirinix/pull/38 was merged since v0.2.0: https://github.com/cloudfoundry-incubator/eirinix/compare/v0.2.0...master Does that mean that the manager...

The status `Message:too old resource version` seems to be an expected behaviour according to kubernetes: https://github.com/kubernetes/kubernetes/issues/22024 It looks like `podwatcher` needs to be updated in order to handle this, rather...

Same problem here on CentOS 7.7 ``` $ rpm -q centos-release centos-release-7-7.1908.0.el7.centos.x86_64 ``` Docker version: ``` $ docker version Client: Docker Engine - Community Version: 20.10.6 API version: 1.41 Go...

Looks like fix is already planned here: https://github.com/cloudfoundry-incubator/kubecf/issues/1730