mlflow-server deployments fail because no charm currently fulfills the kubernetes_manifest.

Bundle builder fails building bundle because mflow-server pod defaults endpoint can't be fulfilled https://test-observer.canonical.com/#/charms/406285?testExecutionId=459039&testResultId=10376235

Start with the bundle builder and the Test Observer execution linked in the issue. Trace why the mlflow-server pod's default endpoint cannot be fulfilled by a Kubernetes manifest, then identify the charm or deployment configuration that must satisfy it. Done means the bundle builds successfully and the mlflow-server deployment no longer reports this fulfillment failure.

Written by the indexing model from the issue text.