Stuck on a 502 Bad Gateway when triggering a scheduled analytics export via a BYOC connector.
The connector is deployed on Azure Kubernetes Service. The endpoint is a simple Flask app that accepts the payload and pushes to Snowflake. Direct curl from the pod works fine. The issue only happens when Genesys Cloud invokes it.
Provider version is 1.12.4. The Terraform resource looks like this:
resource "genesyscloud_byoc_connector" "analytics_export" {
name = "snowflake-export"
description = "Exports OMI to Snowflake"
endpoint = "https://api.example.com/export"
method = "POST"
timeout = 30000
headers {
key = "Authorization"
value = "Bearer ${var.api_key}"
}
}
The response from GC logs shows the request reaches the connector but the connection is reset before the 200 OK is returned. The payload contains roughly 5000 rows of interaction data. Suspecting a TLS handshake issue or an intermediate proxy dropping the connection. The AKS ingress controller logs show a successful 200, but GC reports 502. Any ideas on how to debug the network path between the GC edge and the BYOC endpoint? Is there a specific certificate requirement for BYOC connectors that is not documented?