console connectors endpoint times out

[jason-da-redpanda]

What happened?

New install .. the connectors endpoint /connectors?expand=info&expand=status
timeout

"level":"warn","ts":"2024-08-12T14:30:50.589Z","msg":"failed to list connectors from Kafka connect cluster","cluster_name":"connectors","cluster_address":"http://redpanda-connectors.redpanda.svc.cluster.local:8083/","error":"Get \"http://redpanda-connectors.redpanda.svc.cluster.local:8083/connectors?expand=info&expand=status\": context deadline exceeded"}

What did you expect to happen?

it to not timeout

How can we reproduce it (as minimally and precisely as possible)?. Please include values file.

follow https://docs.redpanda.com/current/deploy/deployment-option/self-hosted/kubernetes/local-guide/

helm repo add redpanda https://charts.redpanda.com/
helm repo update
helm install redpanda redpanda/redpanda \
  --version 5.8.13 \
  --namespace repro \
  --create-namespace \
  --set external.domain=customredpandadomain.local \
  --set statefulset.initContainers.setDataDirOwnership.enabled=true \
  --set connectors.enabled=true \

Anything else we need to know?

it does not reproduce in 5.8.2 ..

Which are the affected charts?

Console, Connectors

Chart Version(s)

$ helm -n <redpanda-release-namespace> list 
# paste output here

Cloud provider

reproduces on kind

JIRA Link: K8S-377

[jason-da-redpanda]

this looks to be due to these being set ...some time between 5.8.2 and 5.8.13

console.config.connect.connectTimeout=0
console.config.connect.readTimeout=0
console.config.connect.requestTimeout=0

intiial test with helmchart

console.config.connect.connectTimeout=15s
console.config.connect.readTimeout=60s
console.config.connect.requestTimeout=6s

looks positive

note...we cannot test with 5.9.4 because of #1511
where connectors break

[david-yu]

Setting the following spec for a cluster using the Operator should help work around this issue:

spec.clusterSpec.console.console.config