[Proposal] Kubernetes target

[anasinnyk]

Hi, It will be awesome if we can transform our Event to Kubernetes manifest and post it to API.

I think a bigger problem here is a templating, because we need to merge our event data with kubernetes manifest data. (I'm not sure if it's a nature for TriggerMash).

Links with similar implementations:

• https://argoproj.github.io/argo-events/sensors/triggers/k8s-object-trigger/
• https://tekton.dev/docs/triggers/triggertemplates/

[jmcx]

Raised at least 2 more times by users wanting to trigger a Kubernetes Job.

[nihar-13]

I have a similar requirement. I have to create and execute a container everytime a particular event is received. I have tried a lot playing around different K8S APIs, but have been half-successful. Here is what I've tried:

1. Created a HTTPPollerSource --> listens to a webpage every 60 secs (lets use a random data generator as example)
2. Created a memory broker (for development)
3. Created a trigger (with no filters as of now)
4. Created a HTTPTarget with target as K8S API (POST) - here I've tried jobs, pods, deployments - everything work once when the HTTPTarget manifest is applied. They dont get triggered upon the next event. The YAML is like this:

Target YAML:

apiVersion: targets.triggermesh.io/v1alpha1
kind: HTTPTarget
metadata:
 name: call-abi-pod
 namespace: default
spec:
  restartPolicy: Always
  response:
    eventType: CallPodResponseEvent
    eventSource: kubernetes-api-response
  skipVerify: true
  endpoint: 'https://kubernetes.docker.internal:6443/apis/batch/v1/namespaces/default/jobs'
  method: 'POST'
  headers:
    Content-type: 'application/yaml'
    data: |
apiVersion: batch/v1
kind: Job
metadata:
  name: sample-abi-job
spec:
  ttlSecondsAfterFinished: 30
  template:
    metadata:
      name: sample-abi-job
    spec:
      containers:
      - name: abi-demo
        image: busybox
        imagePullPolicy: IfNotPresent
        env:
        - name: JOB_LOG_DIR
          value: "/tmp/log/abinitio/" # This should be changed to above line in the actual Ab Initio container
        command:
        - /bin/sh
        - -c
        - mkdir -p ${JOB_LOG_DIR}; echo [`date +"%Y-%m-%d-%H:%M:%S"`]-Hello this is a sample log file from Ab>Initio job. >> ${JOB_LOG_DIR}/fl_scenario.log; echo "Log file written successfully."; cat ${JOB_LOG_DIR}/fl_scenario.log;
      restartPolicy: Never
---