TLS handshake error Vault on EKS with Istio

[QuantumBlueQ]

Describe the bug
I am trying to migrate vault to EKS. As mentioned in the description we also have istio enabled. The certs are on auto. The vault agent injector logs:
2024-08-29T11:43:32.076Z [INFO] handler: Starting handler..
Listening on ":8080"...
2024-08-29T11:43:32.154Z [INFO] handler.auto-tls: Generated CA
2024-08-29T11:43:32.155Z [INFO] handler.certwatcher: Updated certificate bundle received. Updating certs...
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
Error updating MutatingWebhookConfiguration: the server could not find the requested resource
2024-08-29T11:43:41.763Z [ERROR] handler: http: TLS handshake error from 100.68.104.210:35994: no certificate available

To Reproduce
Steps to reproduce the behavior:

1. Deploy vault using basic + we use a helm renderer

Application deployment:

Nothing from default deployment is changed 

Environment

• Kubernetes version: 1.28

• vault-k8s version: 0.24