-
-
Notifications
You must be signed in to change notification settings - Fork 8
fix: Listen on loopback interface so that k8s port-forward works #870
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
NOTE: This required explicitly listening on eth0, otherwise only the loopback interface would be listening.
sbernauer
left a comment
There was a problem hiding this 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( |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point!
See 48c41f4
Fixes #854
defaultsetting aloneI tested this with the getting_started guide (from scratch, with
make run-dev).