Skip to content

Bind internal status check port 9021 to loopback only - #700

Merged
stephanme merged 2 commits into
developfrom
internal-status-loopback
Oct 12, 2026
Merged

stephanme merged 2 commits into
developfrom
internal-status-loopback

Conversation

@stephanme

Copy link
Copy Markdown
Member
  • A short explanation of the proposed change:

/internal/v4/status endpoint on port 9021 is monitored by monit. No need to expose it.

  • An explanation of the use cases your change solves

See also Internal API Docs which claims that port 9021 runs on the loopback interface.

  • Links to any other associated PRs

  • I have viewed signed and have submitted the Contributor License Agreement

  • I have made this pull request to the develop branch

  • I have run CF Acceptance Tests on bosh lite

status=$? was read after `set -e`, so it captured the exit code of
the `set -e` builtin (always 0) instead of curl's. This made the
connection-refused exemption (`status == 7`) dead code.

"exit 1" on 503 (distinct from the killswitch's exit 2).
Before, it was effectively an "exit 0" which is strange for an error
(but worked because monit just checks for the running process).
@stephanme
stephanme force-pushed the internal-status-loopback branch from f468ee0 to b24773e Compare October 5, 2026 15:06
@stephanme
stephanme merged commit 7d6ff62 into develop Oct 12, 2026
2 checks passed
@moleske
moleske deleted the internal-status-loopback branch October 12, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants