-
Notifications
You must be signed in to change notification settings - Fork 204
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
--http-bind-port=80 does not work. binds on 8080 #589
Comments
This bug was addressed in #568, but the it hasn't been released yet. You can give the nightly tag a try ( |
thanks. nightly doesnt appear to listen to anything
|
During the initial initialization, it won't listen on any port. However, after the first fork, it will then select the ports you have chosen. |
i'm not sure what that means but the helm chart install a health check, which is failing because the stats endpoint isnt up, so the container is being deleted |
|
Increase the startup failure threshold ( |
that didnt help. it just never starts listening on port 1042 |
Hi @aep , We'll have a look at your issue. Thanks for reporting. |
Hi @aep , can you specify the version of Helm Charts you're using ? |
I've run some test with version 1.34.1 from Helm Charts, which should be correct according the controller version in your logs, and nothing wrong. I got:
BTW, I've noticed a typo in your command line, you missed the last number in port number. It should be 443 not 44. |
Can you check the logs of your attempt with the official release ? Because it seems that you've got something wrong preventing the computation of the very first transaction and you're stuck with the default haproxy configuration file. If necessary increase the log level by adding the extra args
|
Closed because no activity |
hi,
i'm using the helm chart with useHostNetwork on bare metal to expose haproxy directly on the internet
which starts kubernetes-ingress with
however, this doesnt actually make the ports work. it listens on 8080 anyway.
The text was updated successfully, but these errors were encountered: