Open ntwkninja opened 3 weeks ago
Does this resolve itself after a pepr watcher pod restart? I think in the past we've seen this issue when pepr "stops watching" the endpoints.
We have also floated the idea of adding a config option for end users to specify a CIDR range instead of relying on the pepr watch. We should probably just add that at this point given the inconsistency seen with the watch.
Does this resolve itself after a pepr watcher pod restart? I think in the past we've seen this issue when pepr "stops watching" the endpoints.
I'll try restarting the watcher and report back That worked
Environment
Device and OS: Bottlerocket App version: 1.30 Kubernetes distro being used: AWS EKS Other:
Steps to reproduce
Expected result
netpols for kubeapi update as AWS updates
Actual Result
kubepi addresses are not updated after being initially set
Visual Proof (screenshots, videos, text, etc)
Severity/Priority
Additional Context