Datasets:
|
Download statements/cloudnative-kong-operator-1044.md from CrossSWE/CrossSWE-Bench: direct link, hf CLI and curl.
- Browser
- Download file 479 Bytes
-
https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/statements/cloudnative-kong-operator-1044.md
- Command line
-
hf download hf://datasets/CrossSWE/CrossSWE-Bench/statements/cloudnative-kong-operator-1044.md
-
curl -L -o cloudnative-kong-operator-1044.md https://huggingface.co/datasets/CrossSWE/CrossSWE-Bench/resolve/main/statements/cloudnative-kong-operator-1044.md
479 Bytes
KongRoute reconciliation fails when spec.headers is non-empty because the CRD represents header values differently from the Konnect SDK payload produced by Kong Gateway Operator. The API should support multiple values for each header, and the operator should map that representation to the SDK without dropping or flattening values. Existing KongRoute resources without headers must continue to reconcile, and generated CRD and deepcopy artifacts must match the public Go type.