TLS Handshake: Bad Record MAC

**What happened**:
The pod-identity-webhook fails to deploy tokens with error messages:
```
http: TLS handshake error from 10.42.18.151:33208: local error: tls: bad record MAC
http: TLS handshake error from 10.141.0.253:56136: remote error: tls: bad certificate
```
The bad MAC error is like ~80% of error messages, bad cert is the rest.

**What you expected to happen**:
The webhook deploys the appropriate certs and tokens so my pods can assume a role.

**How to reproduce it (as minimally and precisely as possible)**:
- Deploy the self-hosted setup on an [RKE2](https://github.com/rancher/rke2) cluster
- Create a kubeconfig with a token for the service account for the pod-identity-webhook
- Put that kubeconfig in a secret and mount it to the deployment pod
- Create a service account with the proper annotations
- Create a pod using the service account
- Expect pod to have AWS access

**Anything else we need to know?**:

**Environment**:
- AWS Region: N/A
- EKS Platform version: N/A (running on Rancher RKE2)
- Kubernetes version: v1.28.9+rke2r1
- Webhook Version: 0.5.3

The report names no source files or tests. Start by reproducing the self-hosted setup on an RKE2 cluster with Kubernetes v1.28.9+rke2r1, then inspect the pod-identity-webhook TLS configuration and mounted kubeconfig secret. Done means identifying why the TLS handshake fails and documenting or implementing a verified fix for certificate and token deployment.

Written by the indexing model from the issue text.