chore: back-ports api base path fix

[kleinfreund]

Back-ports a fix for the API base path detection (kumahq/kuma-gui@4c56659) into release-2.x for the patch version release of Kuma 2.0.1.

Signed-off-by: Philipp Rudloff philipp.rudloff@konghq.com

Mode details

• The latest GUI update in the release-2.0 branch is Kuma at f2d11a1ed8ab706b51bdec1b468e53cf32e6c6a2 which includes Kuma GUI at f3dba73d4c264b094b6b351a8b44f2d5a0dc4ecb
• The fix not in Kuma’s release-2.0 branch is Kuma GUI at 4c5665947bb033eea8f1b2e9c86a01d65569226f.

Creating kuma-2.0.1 with fix:

cd kuma-gui
git fetch origin
git switch master
git reset --hard f3dba73d4c264b094b6b351a8b44f2d5a0dc4ecb
git switch --create kuma-2.0.1
git cherry-pick 4c5665947bb033eea8f1b2e9c86a01d65569226f

Building distribution files:

cd kuma-gui
git switch kuma-2.0.1
yarn install
yarn run build

Preparing PR for Kuma:

cd kuma
git switch release-2.x
git pull
git switch --create chore/back-port-api-base-path-fix-for-2.0.1
rm -rf ~/kong/kuma/app/kuma-ui/pkg/resources/data && mkdir -p ~/kong/kuma/app/kuma-ui/pkg/resources/data && cp -r ~/kong/kuma-gui/dist/* ~/kong/kuma/app/kuma-ui/pkg/resources/data

Testing changes:

make dev/tools
make build
KUMA_DP_SERVER_AUTH_TYPE=none make run/universal/memory

Checklist prior to review

• Link to docs PR or issue --
• Link to UI issue or PR --
• Is the issue worked on linked? -- No
• [ ] The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) --
• [ ] The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• [ ] Unit Tests --
• [ ] E2E Tests --
• [ ] Manual Universal Tests --
• [ ] Manual Kubernetes Tests --
• [ ] Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? -- No. This PR is the back port and no other branches need it.
• Do you need to explicitly set a > Changelog: entry here or add a ci/ label to run fewer/more tests? No