Files
Linying Assad 4d7a207363 [fix](docker) Propagate BE registration failures (#66927)
The Kubernetes BE entrypoint scripts initialized `REGISTERED` to the
literal string `false` and later evaluated it with `[[ $REGISTERED ]]`.
In Bash, every non-empty string is true, so an FE registration failure
could be treated as success and the script would continue to start BE
without registering it with FE.

This PR removes the unused string flag and uses the exit status from
`add_self` / `first_deploy_start` directly. Each configured FE address
is tried in order. If all registration attempts fail, the entrypoint
exits before `start_be.sh`, allowing Kubernetes to restart the container
and retry after FE becomes available.

Supersedes #66922, which GitHub automatically closed after its
cross-fork head branch was renamed.

### Release note

Fix Kubernetes BE containers to restart instead of starting unregistered
when FE registration fails.
2026-08-26 19:42:28 +08:00
..