Subscribing Webhook fails despite Webhook pods are running

[steffh]

Describe the bug

As an Airy core user running version 0.28.0,
having the webhook component defined and the configuration applied,
an authenticated request to /webhooks.subscribe returns 409 - { "message": "The webhook component needs to be enabled. Learn more: https://airy.co/docs/core/api/webhook" }
despite the relevant webhook pods are running

To Reproduce

1. Apply configuration for airy.yaml:

kubernetes:
  appImageTag: 0.28.0
  containerRegistry: ghcr.io/airyhq
  namespace: default
  ngrokEnabled: "false"
  host: SOMEHOST
  https: ""
  letsencryptemail: ""
security:
  allowedOrigins: '*'
  systemToken: "SOMETOKEN"
  jwtSecret: SOMESECRET
components:
  integration:
    webhook:
      name: somename
      maxBackoff: 10

2. Checking if the pods are running:

[~/airy-aws] $kubectl get pods                               
NAME                                    READY   STATUS      RESTARTS   AGE
airy-controller-68584474fc-jn9wt        1/1     Running     0          2m33s
api-admin-77fc5569d6-wwz25              1/1     Running     0          6s
api-communication-5cbcc6cfb8-84295      1/1     Running     0          2m34s
api-websocket-bbc64484-m5bjb            1/1     Running     0          3m52s
beanstalkd-0                            2/2     Running     0          66d
frontend-chat-plugin-79db79cbdc-7pg8l   1/1     Running     0          9m47s
frontend-ui-d4494c76b-n2qgb             1/1     Running     0          9m45s
helm-runner-cck9z                       0/1     Completed   0          66d
kafka-0                                 1/1     Running     0          66d
provisioning-topics-k9zdf               0/1     Completed   0          66d
schema-registry-6c48f6f9f6-l7j5j        1/1     Running     0          66d
sources-chatplugin-cd78655dd-5pml4      1/1     Running     0          3m51s
wait-for-api-communication-p9nmg        0/1     Completed   0          66d
wait-for-frontend-chat-plugin-28rx9     0/1     Completed   0          66d
wait-for-frontend-ui-r8fzz              0/1     Completed   0          66d
webhook-consumer-7c9d9d8b98-xvwcc       1/1     Running     0          6m25s
webhook-publisher-575696bcb8-62m48      1/1     Running     0          6m25s
zookeeper-0                             1/1     Running     0          66d

3. Send an authenticated request to /webhooks.subscribe:

Expected behavior

The request should return HTTP 200 and the webhook pod should start sending events.

Environment:

• Cloud: AWS