K8 Sensor pod starting with incorrect Service Account

[markday1962]

Hi, I am new to argo events, I have created a k8s sensor with the following service account

The sensor.argoproj.io/incoming-webhook-k8 spec shows the correct service account

spec:
dependencies:

• eventName: nn-search-service
  eventSourceName: incoming-webhook
  name: payload
  loggingFields: null
  template:
  serviceAccountName: argo-events-sa

But when an event triggers the pod that gets created has the default service account assigned to it and fails (I am doing a kubectl get pods)

apiVersion: v1
kind: Pod
metadata:
creationTimestamp: "2023-08-01T12:37:25Z"
generateName: payload-
labels:
app: payload
events.argoproj.io/action-timestamp: "1690893445507"
events.argoproj.io/sensor: incoming-webhook-k8
events.argoproj.io/trigger: payload
name: payload-tgb5m
namespace: argo-events
resourceVersion: "46612884"
uid: aebf6dad-4a86-4c4d-be23-4c9d336b97ba
spec:
containers:

• args:
  • get
  • pods
    command:
  • kubectl
    image: alpine/k8s:1.24.16
    imagePullPolicy: IfNotPresent
    name: hello
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
  • mountPath: /var/run/secrets/kubernetes.io/serviceaccount
    name: kube-api-access-hn6kz
    readOnly: true
    dnsPolicy: ClusterFirst
    enableServiceLinks: true
    nodeName: ip-10-30-9-77.eu-west-1.compute.internal
    preemptionPolicy: PreemptLowerPriority
    priority: 0
    restartPolicy: Never
    schedulerName: default-scheduler
    securityContext: {}
    serviceAccount: default
    serviceAccountName: default

Am I doing something wrong??

Regards Mark