All geek questions in one place

Generic IP Address in CoreOS

I am studying the use of CoreOS at work and for several projects where I do not want to have a single point of failure. CoreOS and Docker look promising, and I can hipache work with a messenger container talking to the service. Basically, it can work.

But what about shared public IP? How should this problem be solved? I can not find good documentation on this. http://www.keepalived.org/ looks like something that could solve this problem. But is this the right tool in this situation?

Am I missing something? Why don't people talk about this problem anymore?

+4
source share
2 answers

There are several different ways to take care of this. If you are using a cloud computing provider (EC2 / OpenStack / Google Compute Engine), there is the concept of a floating IP address that can be moved around an API call. This eliminates the need to use things like VRRP.

Ultimately, this is best used using short TTL DNS records. Using this method also allows you more flexibility in using location-oriented applications (where DNS in different regions can be routed to the nearest place), simple transition to IPv6, and switching to another resource without the need to maintain your own internal routing infrastructure.

+2
source

keepalived, ip init- node Coreos

  - name: local-paas-ip.service
    command: start
    content: |
    [Unit]
    Description=Receive traffic from keepalived floating ip

    [Service]
    ExecStart=/usr/bin/sudo /usr/bin/ip addr add XXX.XXX.XXX.XXX dev lo:1

/, , - .

0

Source: https://habr.com/ru/post/1540101/

More articles:


All Articles