Prefect Server Kubernetes deployment requires prefectApiUrl be set after 3.1 release

[tjordahl]

Bug summary

When upgrading to Prefect 3.1.2, I had to explicitly set the prefectApiUrl in my values.yaml file of the prefect-server helm chart.
This is the URL that the web UI uses instead of the hostname in the UI URL.

Looking at the network calls, Prefect 2.x UI calls ui-settings:

{
    "api_url": "/api",
    "csrf_enabled": false,

Prefect 3.x calls ui-settings:

{
    "api_url": "https://prefect.my.internal.domain/api",
    "csrf_enabled": false,

I should be able to get the Prefect 2.x/3.0 behavior of using the hostname from the page so I do not have to hard code the Api URL in my helm charts. I use the same values.yaml file for all of my Prefect environments (e.g. prefect-stage, prefect-prod).

Version info

Version:             3.1.2
API version:         0.8.4
Python version:      3.12.7
Git commit:          02b99f0a
Built:               Tue, Nov 12, 2024 1:38 PM
OS/Arch:             linux/x86_64
Profile:             ephemeral
Server type:         server
Pydantic version:    2.9.2

Additional context

No response