[release-1.27] path normalization affecting kubectl proxy conformance test for /api endpoint

[VestigeJ]

Environmental Info:
K3s Version:

v1.27.2-rc2+k3s1

Node(s) CPU architecture, OS, and Version:

Linux ip-172-31-21-199 5.14.21-150400.24.11-default #1 SMP PREEMPT_DYNAMIC Sun Jul 17 20:46:33 UTC 2022 (be260ca) x86_64 x86_64 x86_64 GNU/Linux

Cluster Configuration:

3 server 1 agent

Describe the bug:

sonobuoy e2e conformance test caught an issue with curling the /api endpoint

Steps To Reproduce:

• Installed K3s:

Install k3s attempt to curl the default api port

kubectl -v=6 get --raw /api/

Expected behavior:

curl command succeeds and reports pertinent information

Actual behavior:

I0523 23:29:19.379962    2339 loader.go:373] Config loaded from file:  /etc/rancher/k3s/k3s.yaml
I0523 23:29:19.382887    2339 round_trippers.go:553] GET https://127.0.0.1:6443/api/ 404 Not Found in 2 milliseconds
I0523 23:29:19.383137    2339 helpers.go:246] server response object: [{
  "metadata": {},
  "status": "Failure",
  "message": "the server could not find the requested resource",
  "reason": "NotFound",
  "details": {},
  "code": 404
}]

Additional context / logs:
only present on v1.26.5 and v1.27.2 release candidates.

[VestigeJ]

$ sono_results

Plugin: e2e
Status: passed
Total: 7211
Passed: 382
Failed: 0
Skipped: 6829

Plugin: systemd-logs
Status: passed
Total: 4
Passed: 4
Failed: 0
Skipped: 0

Run Details:
API Server version: v1.27.2-rc3+k3s1
Node health: 4/4 (100%)
Pods health: 16/16 (100%)