Marcel Zięba

/scale-100

@jshr-w would you take a look at results of scale-test? It seems like we are still seeing unreachable endpoints / nodes:  before:  so it seems like with rate-limiting...

From the logs you provided for `ip-10-157-24-164.eu-west-3.compute.internal` I can see the following ones: ``` 2024-10-15 13:50:18.222 time="2024-10-15T11:50:18Z" level=warning msg="Failed to update CiliumNode" attempt=0 error="Operation cannot be fulfilled on ciliumnodes.cilium.io \"ip-10-157-24-164.eu-west-3.compute.internal\":...

> The log come from [pkg/aws/eni/node.go#L573](https://github.com/cilium/cilium/blob/810f3825d66f7c6dce047e39bb0f46986f648eaf/pkg/aws/eni/node.go#L573) ? Yes, this log comes from there. So I think most likely is that instance information in cilium-operator's cache is stale somehow and doesn't...

> The CFP process doesn't necessarily need to encompass this - we could just publish guidelines on individual repositories and deal with feature maturity as part of the code review...

@sayboras based on Nick's comment I guess we should close this PR?

/test

GCP CCM seems to have been fixed in https://github.com/kubernetes/kops/pull/17348 and is now pinned to specific version.

side note: I think there are multiple valid concerns that this CFP describes, but it's a bit unclear to me what is the user story that we are trying to...

cc @dylandreimerink @jrife to make sure if I got it right from https://github.com/cilium/cilium/issues/41245 that it also makes sense to add it from map pruning perspective. FYI, I was mostly interested...