Skip to content

Conversation

@NickLarsenNZ
Copy link
Member

@NickLarsenNZ NickLarsenNZ commented Nov 20, 2025

Fixes #854

  • Listen on loopback so that k8s port-forwards work
  • Explicitly listen on eth0 (otherwise only the loopback is listened on)
  • I left the existing default setting alone

I tested this with the getting_started guide (from scratch, with make run-dev).

NOTE: This required explicitly listening on eth0, otherwise only the loopback interface would be listening.
@NickLarsenNZ NickLarsenNZ self-assigned this Nov 20, 2025
@NickLarsenNZ NickLarsenNZ moved this to Development: In Progress in Stackable Engineering Nov 20, 2025
@NickLarsenNZ NickLarsenNZ moved this from Development: In Progress to Development: Waiting for Review in Stackable Engineering Nov 20, 2025
sbernauer
sbernauer previously approved these changes Nov 21, 2025
Copy link
Member

@sbernauer sbernauer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice, thanks!
Tested on IONOS, port-forward, NodePort and LoadBalancer all work

"nifi.web.https.network.interface.default".to_string(),
"".to_string(),
);
properties.insert(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please add a short comment on why we do it this way here?
Basically that the situation sucks, we rely on eht0 being present (WCGW? :D), mostly summarizing stuff you already written down + a link to #854

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point!
See 48c41f4

@sbernauer sbernauer moved this from Development: Waiting for Review to Development: In Review in Stackable Engineering Nov 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Development: In Review

Development

Successfully merging this pull request may close these issues.

Bind to 0.0.0.0 (or at least 127.0.0.1) to support port-forwards

3 participants