Flagd UI is not reachable after Kubernetes deployment with kubectl

[CyanideCentral]

Bug Report

I'm using this commit: c8a9a91

Symptom

After deploying the demo on Kubernetes using kubectl and the kubernetes/opentelemetry-demo.yaml file, all services run normally but Flagd UI is not reachable.
Expected: Flagd UI reachable at localhost:8080/feature
Actual: “no healthy upstream” error.

Reproduce

1. Deploy the demo on a Kind cluster (Kind v0.30.0) with: kubectl create --namespace otel-demo -f https://raw.githubusercontent.com/open-telemetry/opentelemetry-demo/main/kubernetes/opentelemetry-demo.yaml

2. Set port forward with: kubectl --namespace otel-demo port-forward svc/frontend-proxy 8080:8080

3. Access localhost:8080/feature

Additional Context

Flagd UI works normally after Helm installation. The above issue is caused by the frontend proxy seeing FLAGD_UI_HOST defined as flagd-ui while it should route /feature to pod "flagd" instead. (flagd-ui runs inside the flagd pod.)

opentelemetry-demo/kubernetes/opentelemetry-demo.yaml

Lines 19275 to 19276 in c8a9a91

	- name: FLAGD_UI_HOST
	value: flagd-ui

Changing line 19276 to "flagd" resolves the issue.

_{Tip: React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}