Robin Gögge

/test

/test

/ci-l7

Would you be able to provide a sysdump for at least one of the clusters?

The locations for the generated files are suggestions for now. I'm also wondering how we should remove some of them, based on configuration changes.

The output of a config dump now looks like this: ``` root@kind-control-plane:/home/cilium# cat /var/run/cilium/state/dp_config/devices/eth0/bpf_network.json {"AllowIcmpFragNeeded":true,"DeviceMTU":1500,"EnableExtendedIPProtocols":false,"EnableIcmpRule":true,"EnableL2Announcements":false,"EnableNetkit":false,"EnableNoServiceEndpointsRoutable":true,"EnableRemoteNodeMasquerade":false,"EthHeaderLength":14,"HostEpID":2203,"InterfaceIfindex":595,"InterfaceMAC":[2,66,172,18,0,2,0,0],"L2AnnouncementsMaxLiveness":0,"NATIPv4Masquerade":[0,0,0,0],"NATIPv6Masquerade":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0],"SecurityLabel":1,"VtepMask":0,"WgIfindex":0,"WgPort":0,"DirectRoutingDevIfindex":0,"HybridRoutingEnabled":false,"PolicyDenyResponseEnabled":false,"RouterIPv6":[253,0,0,16,2,68,0,0,0,0,0,0,0,0,179,77],"ServiceLoopbackIPv4":[169,254,42,1],"ServiceLoopbackIPv6":[254,128,0,0,0,0,0,0,0,0,0,0,0,0,0,1],"SupportsFibLookupSkipNeigh":true,"TracePayloadLen":128,"TracePayloadLenOverlay":192,"TracingIPOptionType":0} ``` Happy to remove the second commit, or make the cleanup less eager.

How was `CLUSTER_ID` previously written to `node_config.h` at runtime? This PR now adds writing `option.Config.CluderID` to the `Node` object, but doesn't remove any code that was previously setting it :thinking:

/test

This will need more information to be investigated. Do you have clear steps to reproduce this, best case locally with kind? And did you try taking a sysdump? If you...