benchmark in v0.9 stopped supporting k3s

[ksandowi]

I was able to deploy ChatQnA (0.9) using k3s and perform benchmark tests:

• v0.8 successfully

• v0.9 with below exception
  Exception when retrieving ConfigMap: (404)
  Reason: Not Found
  HTTP response headers: HTTPHeaderDict({'Audit-Id': '6e3d2e0b-c54d-4635-9d1c-d761c1de7ae1', 'Cache-Control': 'no-cache,
  private', 'Content-Type': 'application/json', 'X-Kubernetes-Pf-Flowschema-Uid': 'dd679818-0931-40a3-978f-f5de129f6bb5', 'X-Kubernetes-Pf-Prioritylevel-Uid': '746bc387-43d5-4ad2-91cf-1978f7afa33c', 'Date': 'Wed, 11 Sep 2024 09:18:34 GMT', 'Content-Length': '208'})
  HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"configmaps "kubelet-config" not found","reason":"NotFound","details":{"name":"kubelet-config","kind":"configmaps"},"code":404}

  This is because (v0.9) benchmark tests depends on vanilla kubernetes (k8s) configuration (kubelet-config in ConfigMap), which is not set by k3s.

Please consider enable support for k3s without dependency for vanilla kubernetes (k8s).
If I deploy ChatQnA (0.9) using vanilla kubernetes (k8s), I was able to perform both (0.8 and 0.9) benchmark tests successfully

[chickenrae]

Should this be closed?

[ksandowi]

OPEA benchmark still doesn't support k3s because it depends on k8s configuration parameters

[chickenrae]

What would next steps be?

[ksandowi]

If OPEA benchmark team decide to stop supporting k3s and support only vanilla kubernetes, than this issue can be closed.
Otherwise OPEA benchmark team should prepare benchmark without k8s dependency