Kubernetes Discover wizard is not able to validate connectivity when IP pinning is enabled

[webvictim]

Expected behavior

When running the Kubernetes "Test Connection" wizard in the web UI, this flow should complete successfully if the user's role has spec.options.pin_source_ip: true

Current behavior

The "Test Connection" step fails with the error pinned IP doesn't match observed client IP

If it's not possible to fix this, we should squash or otherwise filter the error.

Connectivity works fine from the CLI after running tsh kube login <name>.

Auth server logs report:

May 16 18:40:06 ip-172-31-3-140.ec2.internal teleport[3726]: 2024-05-16T18:40:06Z WARN [PROXY:SER] pinned IP doesn't match observed client IP pid:3726.1 authz/permissions.go:562

Bug details:

• Teleport version: 15.3.4