Describe the bug
Components built on the eventing receive adapter framework (pkg/adapter/v2) never start the pprof HTTP server, making runtime profiling a no-op even when runtime-profiling: "enabled" is set in the observability ConfigMap.
MainWithInformers creates a ProfilingServer and correctly passes it to SetupObservabilityOrDie (which sets the enabled flag and logs "Profiling enabled: true"), but never calls ListenAndServe. Port 8008 is never bound.
Expected behavior
Setting runtime-profiling: "enabled" in the observability ConfigMap should cause the pprof endpoints (/debug/pprof/) to become accessible on port 8008 for adapter-based components, matching the behaviour of sharedmain-based components.
To Reproduce
- Deployed receive adapter server (This is one I am using)
- Set
runtime-profiling: "enabled" in the config-observability ConfigMap
- The server logs
{"level":"info","ts":"2026-04-01T12:58:53.568Z","logger":"pipelinesascode.pprof","caller":"k8s/pprof.go:51","msg":"Profiling enabled: true",xxx}
- Attempt to curl
http://<adapter-pod>:8008/debug/pprof/ — connection refused
Knative release version: tag v0.48.1
Describe the bug
Components built on the eventing receive adapter framework (
pkg/adapter/v2) never start the pprof HTTP server, making runtime profiling a no-op even whenruntime-profiling: "enabled"is set in the observability ConfigMap.MainWithInformerscreates aProfilingServerand correctly passes it toSetupObservabilityOrDie(which sets the enabled flag and logs"Profiling enabled: true"), but never callsListenAndServe. Port 8008 is never bound.Expected behavior
Setting
runtime-profiling: "enabled"in the observability ConfigMap should cause the pprof endpoints (/debug/pprof/) to become accessible on port 8008 for adapter-based components, matching the behaviour of sharedmain-based components.To Reproduce
runtime-profiling: "enabled"in theconfig-observabilityConfigMaphttp://<adapter-pod>:8008/debug/pprof/— connection refusedKnative release version: tag v0.48.1