Skip to content
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.

Sign up for GitHub

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

Jump to bottom

FAQ: Expose public static IPs #388

Closed
wants to merge 3 commits into from
Closed

FAQ: Expose public static IPs #388

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1d5a91c
add use kubectl with RBAC to FAQ
drnickiw Feb 11, 2019
74e547d
Add path to expose public static IPs
drnickiw Feb 18, 2019
41b822f
remove use kubectl file
drnickiw Feb 19, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 29 additions & 0 deletions content/faq/path-to-expose-public-static-ips.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
title: "Is there a path to exposing public static IPs?"
description: "Static IPs of services running inside the cluster are trivial. However, externally available public IPs are a different story."
tags:
- static IP
- public IP
- AWS
- Network Load Balancer
---

## Question

Is there a straightforward path to exposing public static IPs for services?

## Answer

Static IPs of services running inside the cluster are trivial. Simply specify the `ClusterIP` field in the pod spec. However, externally available public IPs are a different story. This is now possible with the new Network Load Balancers (NLBs) on AWS (announced last re:invent) However, we haven't tried using them yet with Kubernetes.

It’s quite easy to implement though. Simply add the following annotation to the Service Load Balancer for the ingress to switch from the default mode of `elb` to `nlb`.

```
annotations:
# by default the type is elb (Classic Load Balancer).
service.beta.kubernetes.io/aws-load-balancer-type: nlb```

Read more [here.](https://github.com/kubernetes/ingress-nginx/blob/master/deploy/provider/aws/service-nlb.yaml)


NLBs are highly performant and the superior option in the long run. See [here.](https://aws.amazon.com/blogs/aws/new-network-load-balancer-effortless-scaling-to-millions-of-requests-per-second/)