Skip to content

Profiling server not starting in the adapter framework #9007

@theakshaypant

Description

@theakshaypant

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

  1. Deployed receive adapter server (This is one I am using)
  2. Set runtime-profiling: "enabled" in the config-observability ConfigMap
  3. 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}
  1. Attempt to curl http://<adapter-pod>:8008/debug/pprof/ — connection refused

Knative release version: tag v0.48.1

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/bugCategorizes issue or PR as related to a bug.triage/acceptedIssues which should be fixed (post-triage)

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions