eventing: When the data plane can't reach the apiserver, it silently fails to forward
Describe the bug
In a non-default namespace, the default-broker-filter deployment fails to actually load any Trigger data, and instead reports:
sigs.k8s.io/controller-runtime/pkg/cache/internal/informers_map.go:126: Failed to list *v1alpha1.Trigger: Get https://10.15.240.1:443/apis/eventing.knative.dev/v1alpha1/namespaces/demo/triggers?limit=500&resourceVersion=0: net/http: TLS handshake timeout
and
jsonPayload: {
caller: "filter/main.go:52"
error: "Get https://10.15.240.1:443/api?timeout=32s: dial tcp 10.15.240.1:443: connect: connection refused"
level: "fatal"
logger: "provisioner"
msg: "Error starting up."
stacktrace: "main.main
/go/src/github.com/knative/eventing/cmd/broker/filter/main.go:52
runtime.main
/usr/local/go/src/runtime/proc.go:200"
ts: "2019-04-18T22:36:24.188Z"
}
Expected behavior
Broker and Trigger work in a namespace other than the default namespace.
To Reproduce Deploy Broker/Trigger to a non-default namespace and then attempt to deliver via Trigger.
Knative release version Release 0.5
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Comments: 17 (16 by maintainers)
I don’t think this is caused by using a Broker in a non-default namespace. The Broker e2e tests have been running in a non-default namespace since their creation.
TestDefaultBrokerWithManyTriggers runs in a non-default namespace (its name is generated here).