how to enable extension trace from apiserver in chart

[yingxin-gh]

Description

Install kelemetry by helm, but can not see the audit event in k8s resource trace. It can see the audit event by kind setup to uncomment the extension trace config in tfconfig.yaml. How to enable or config them in helm install ?

User story

No response

[SOF3]

The default configuration already displays audit. The "Extension trace" is a new feature that allows you to integrate trace data from other sources, which is currently not very well-documented yet.

The DEPLOY.md guide should have already configured all the required default settings to show audit and events in the trace. If it doesn't, please check each step in the deployment chain:

• Did you configure the apiserver to send audit events through audit webhook?
• Are all the kelemetry pods running healthily?
• Any logs from the pods indicating they are working? Or any error logs?

[yingxin-gh]

Yes, this is my config. And I follow the DEPLOY.md to install kelemetry in our cluster.

# kubectl get svc kelemetry-webhook
NAME                TYPE           CLUSTER-IP     EXTERNAL-IP    PORT(S)          AGE
kelemetry-webhook   LoadBalancer   10.97.91.250   x.x.x.x   8080:30754/TCP   5d

# cat /etc/kubernetes/audit/audit-kubeconfig.yaml
apiVersion: v1
clusters:
- cluster:
    server: http://<ingress hosts address>/audit/tracetest  ---tracetest should be the cluster name ?
  name: audit
contexts:
- context:
    cluster: audit
  name: main
current-context: main
kind: Config
preferences: {}

# kubectl get po
NAME                                   READY   STATUS    RESTARTS        AGE
kelemetry-collector-6677dcd78c-jrx2j   1/1     Running   6 (4d5h ago)    4d5h
kelemetry-collector-6677dcd78c-s6fvd   1/1     Running   6 (4d5h ago)    4d5h
kelemetry-collector-6677dcd78c-w4hpg   1/1     Running   6 (4d5h ago)    4d5h
kelemetry-consumer-5888f6496c-2rbrl    1/1     Running   0               4d4h
kelemetry-consumer-5888f6496c-sh8vn    1/1     Running   0               4d4h
kelemetry-consumer-5888f6496c-wdf5p    1/1     Running   0               4d4h
kelemetry-etcd-0                       1/1     Running   0               4d5h
kelemetry-etcd-1                       1/1     Running   0               4d5h
kelemetry-etcd-2                       1/1     Running   0               4d5h
kelemetry-frontend-7c6d94cd76-5gx8n    2/2     Running   14 (4d5h ago)   4d5h
kelemetry-frontend-7c6d94cd76-6ngs2    2/2     Running   4 (5d ago)      5d
kelemetry-frontend-7c6d94cd76-tqp56    2/2     Running   4 (5d ago)      5d
kelemetry-informers-b49dffc84-g2z8w    1/1     Running   0               4d5h
kelemetry-informers-b49dffc84-ht4zw    1/1     Running   0               5d
kelemetry-informers-b49dffc84-smfvf    1/1     Running   0               5d
kelemetry-storage-0                    1/1     Running   0               4d5h

[SOF3]

Yes, in the case here, change tracetest to tu932.