Datasets:
|
Download statements/cloudnative-kong-operator-1723.md from CrossSWE/CrossSWE-Bench: direct link, hf CLI and curl.
- Browser
- Download file 577 Bytes
-
https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/statements/cloudnative-kong-operator-1723.md
- Command line
-
hf download hf://datasets/CrossSWE/CrossSWE-Bench/statements/cloudnative-kong-operator-1723.md
-
curl -L -o cloudnative-kong-operator-1723.md https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/statements/cloudnative-kong-operator-1723.md
577 Bytes
ControlPlane resources are being migrated to the v2alpha1 API, but several Kong Gateway Operator reconciliation and indexing paths still assume the older type. This can break ControlPlane/DataPlane reconciliation, especially when the ingress controller is started with an already-created Kubernetes client configuration. The operator should use the v2alpha1 contract consistently, and the ingress controller integration should accept the supplied client configuration without rebuilding or discarding it. Existing manager startup and reconciliation behavior must remain intact.