HAProxy - Ability to listen to a specific IP address #12848

Closed
jwendell opened this Issue Feb 7, 2017 · 7 comments

Comments

Projects
None yet
5 participants
@jwendell
Contributor

jwendell commented Feb 7, 2017

Starting origin with the flags --listen and --master is not enough to make haproxy to listen on the specified ip address.

This would be useful in a scenario where one wants to have more than one origin instance running on the same host, having multiple IP addresses.

@jwendell

This comment has been minimized.

Show comment
Hide comment
@jwendell

jwendell Feb 7, 2017

Contributor

I'm cooking a PoC patch for this enhancement (can't assign myself it seems...)

Contributor

jwendell commented Feb 7, 2017

I'm cooking a PoC patch for this enhancement (can't assign myself it seems...)

@pweil-

This comment has been minimized.

Show comment
Hide comment
@pweil-

pweil- Feb 7, 2017

Member

#12175 is relevant to this discussion but hasn't moved in a while. @knobunc @ramr we may just need to close it out.

Member

pweil- commented Feb 7, 2017

#12175 is relevant to this discussion but hasn't moved in a while. @knobunc @ramr we may just need to close it out.

@pweil-

This comment has been minimized.

Show comment
Hide comment
@pweil-

pweil- Feb 7, 2017

Member

@jwendell @knobunc I also want to note that in the past we've recommended to just use a custom template for something like this rather than add to the variables that we already support. Using a config map would mean that you do not need to build a new image in order to consume a custom template.

Member

pweil- commented Feb 7, 2017

@jwendell @knobunc I also want to note that in the past we've recommended to just use a custom template for something like this rather than add to the variables that we already support. Using a config map would mean that you do not need to build a new image in order to consume a custom template.

@jwendell

This comment has been minimized.

Show comment
Hide comment
@jwendell

jwendell Feb 7, 2017

Contributor

Here's the work in progress: https://github.com/openshift/origin/compare/master...jwendell:haproxy-bind?expand=1

It's still missing docs, but it's kind of working. Need to investigate a bug though. When I start a second openshift instance, the router on the first one stops working...

Contributor

jwendell commented Feb 7, 2017

Here's the work in progress: https://github.com/openshift/origin/compare/master...jwendell:haproxy-bind?expand=1

It's still missing docs, but it's kind of working. Need to investigate a bug though. When I start a second openshift instance, the router on the first one stops working...

@openshift-bot

This comment has been minimized.

Show comment
Hide comment
@openshift-bot

openshift-bot Feb 9, 2018

Member

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

Member

openshift-bot commented Feb 9, 2018

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-bot

This comment has been minimized.

Show comment
Hide comment
@openshift-bot

openshift-bot Mar 12, 2018

Member

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

Member

openshift-bot commented Mar 12, 2018

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-bot

This comment has been minimized.

Show comment
Hide comment
@openshift-bot

openshift-bot Apr 12, 2018

Member

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Member

openshift-bot commented Apr 12, 2018

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment