Marcin Skalski
Marcin Skalski
Applying steps from issue description ends with error on zone: ``` 2024-05-17T08:28:55.172Z INFO kds-delta-zone creating a new resource from upstream {"type": "MeshTimeout", "name": "mesh-timeout-all-default-bv8z44b7bzb99xc7.kong-mesh-system", "mesh": "default"} 2024-05-17T08:28:55.292Z INFO kds-delta-zone error...
xref: https://github.com/kumahq/kuma/issues/10260
Due to the nature of delta KDS, force deleted resource on global reappears after restarting zone, or changing resource with the same type on zone. Ideally, after force deleting resource...
It would be great to have as GitHub just drastically decreased limits for using unauthenticated API calls. https://github.blog/changelog/2025-05-08-updated-rate-limits-for-unauthenticated-requests/#why-were-updating @raviqqe are there any on adding this? Or some other way of...
It turns out that github increased the limits, so it is no longer the issue. Also, I've testes it and auth header didn't work in this situation. What would be...
closing as we won't be working on this any time soon, we can reopen this in the future
closing as we now use mise for tools dependency management
It also some times fail with OOM locally: ``` for i in $( find pkg/plugins/policies -name '*.yaml' | grep '/api/' | grep -v '/testdata/'); do DIR=/Users/[email protected]/kong/mesh/testing/kuma/build/oapitmp/policies/$(echo ${i} | awk -F/...
fixed by: https://github.com/kumahq/kuma/pull/14226
@johncowen I think now we can use KRI for this. Do are we keeping this issue or do we have some other issue for using KRI?