webhook implementation

[msvinaykumar]

Description

The webhook parameter allows the system to notify an external service or consumer about the completion status of
an experiment-processing job. When a job is completed, this webhook will be triggered to send an HTTP request to a
predefined URL, configured either via an environment variable (webhookURL) or within a kruize configuration
file.
This notification mechanism is essential for systems that require real-time updates about the job's processing
status, enabling consumers to take immediate follow-up actions. For example, an external analytics dashboard, a
monitoring service, or a message queue like Kafka can listen for these webhook calls to further process or log the
job completion data.

Fixes # (issue)

Type of change

• Bug fix
• New feature
• Docs update
• Breaking change (What changes might users need to make in their application due to this PR?)
• Requires DB changes

How has this been tested?

Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.

• New Test X
• Functional testsuite

Test Configuration

• Kubernetes clusters tested on:

Checklist 🎯

• Followed coding guidelines
• Comments added
• Dependent changes merged
• Documentation updated
• Tests added or updated

Additional information

Include any additional information such as links, test results, screenshots here

[dinogun]

@msvinaykumar I think the implementation is unnecessarily adding complexity. What we need is to embed the webhook as part of the Bulk API itself.

{
  "filter": {
    "exclude": {
      "namespace": [],
      "workload": [],
      "containers": [],
      "labels": {}
    },
    "include": {
      "namespace": [],
      "workload": [],
      "containers": [],
      "labels": {
        "key1": "value1",
        "key2": "value2"
      }
    }
  },
  "time_range": {},
  "datasource": "prometheus-1",
  "experiment_types": [
    "container",
    "namespace"
  ]
  "webhooks": {
      "default": "http://URL:PORT/bulkAPIDefaultWebhook",
      "Error": ""http://URL:PORT/bulkAPIErrorWebhook"
  }
}

Also what gets posted on the Webhook is the BulkAPI response as-is.

[dinogun]

@msvinaykumar Please fix the conflicts

[msvinaykumar]

@msvinaykumar I think the implementation is unnecessarily adding complexity. What we need is to embed the webhook as part of the Bulk API itself.

{
  "filter": {
    "exclude": {
      "namespace": [],
      "workload": [],
      "containers": [],
      "labels": {}
    },
    "include": {
      "namespace": [],
      "workload": [],
      "containers": [],
      "labels": {
        "key1": "value1",
        "key2": "value2"
      }
    }
  },
  "time_range": {},
  "datasource": "prometheus-1",
  "experiment_types": [
    "container",
    "namespace"
  ]
  "webhooks": {
      "default": "http://URL:PORT/bulkAPIDefaultWebhook",
      "Error": ""http://URL:PORT/bulkAPIErrorWebhook"
  }
}

Also what gets posted on the Webhook is the BulkAPI response as-is.

Implemented

[dinogun]

LGTM