How To Connect Kubernetes Service To Amazon Route 53

[Sebastian Jordan]

Hi,
I want to run an application on a kubernetes cluster.  The cluster is running on "bare metal".  Now I want to offer said application as a service publicly.  I know that there is the NodePort option for services which allows users to reach the service from outside of the cluster.  I understand that this means that traffic might/will be duplicated because I cannot know in advance which nodes run the pods implementing the service.  Now my question:

Is there a plugin of some sorts that "connects" a kubernetes service to Route 53 so that Route 53 routes traffic to a node running the service directly and also implements some sort of fault tolerance, e.g. "retry on failure" when route 53 job quota kicks in?

The migration path to kubernetes is not an easy one for me.  For that reason I would like to stay at route 53 to not make it more difficult for me.

Cheers,
Sebastian

[Rodrigo Campos]

On Tuesday, November 8, 2016, Sebastian Jordan <jor...@schneevonmorgen.com> wrote:

Hi,
I want to run an application on a kubernetes cluster.  The cluster is running on "bare metal".  Now I want to offer said application as a service publicly.  I know that there is the NodePort option for services which allows users to reach the service from outside of the cluster.  I understand that this means that traffic might/will be duplicated because I cannot know in advance which nodes run the pods implementing the

This means kubernetes does the route it internally to the node it has the pod, etc. But that is inside the cluster, usually just LAN connections.

 

 service.  Now my question:

Is there a plugin of some sorts that "connects" a kubernetes service to Route 53 so that Route 53 routes traffic to a node running the service 

Why not ingress or service type load balancer and point the dns record there?

 

directly and also implements some sort of fault tolerance, e.g. "retry on failure" when route 53 job quota kicks in?

When job quota kicks in? Sorry, don't follow you. Can you please elaborate?

[Sebastian Jordan]

Hi,

thank you for your reply.

Am Dienstag, 8. November 2016 13:15:17 UTC+1 schrieb Rodrigo Campos:

On Tuesday, November 8, 2016, Sebastian Jordan <jor...@schneevonmorgen.com> wrote:

Hi,
I want to run an application on a kubernetes cluster.  The cluster is running on "bare metal".  Now I want to offer said application as a service publicly.  I know that there is the NodePort option for services which allows users to reach the service from outside of the cluster.  I understand that this means that traffic might/will be duplicated because I cannot know in advance which nodes run the pods implementing the

This means kubernetes does the route it internally to the node it has the pod, etc. But that is inside the cluster, usually just LAN connections.

Routing inside of the cluster is something that does not work for my use case.  It is just too much traffic.
 

 

 service.  Now my question:

Is there a plugin of some sorts that "connects" a kubernetes service to Route 53 so that Route 53 routes traffic to a node running the service 

Why not ingress or service type load balancer and point the dns record there?

A LoadBalancer is either implemented by a cloud provider or as a NAT (or reverse proxy), which also means that all traffic gets duplicated.
 

 

directly and also implements some sort of fault tolerance, e.g. "retry on failure" when route 53 job quota kicks in?

When job quota kicks in? Sorry, don't follow you. Can you please elaborate?

Job quota is one example, service is not reachable is another problem that might occur.  The mechanism/plugin to inform Route53 has to handle these cases gracefully.

Thank you for your time,
Sebastian