This document introduces inlets, a tool that provides public IPs for Kubernetes clusters by tunneling traffic through a proxy. It discusses how the number of available IPv4 addresses has been exhausted, and how inlets addresses this by tapping into unused IP address stockpiles from cloud providers. The document outlines several use cases for inlets including webhook integrations, chatops, and IoT command and control. It also provides an overview of the inlets operator for Kubernetes and the roadmap for future inlets features and services.
Right Money Management App For Your Financial Goals
Still waiting for IPv6? Try the inlets-operator
1. Still waiting for IPv6?
Get a public IP for your Kubernetes
Cluster with inlets
Alex Ellis, Founder @ OpenFaaS Ltd
Meet OpenFaaS @ KubeCon => http://bit.ly/2Oeodlm
2. @inletsdev
AGENDA
2
• IPv4 is dead, long live IPv4
• Introducing inlets
• Use-cases and case-studies
• inlets-operator for Kubernetes
• What’s next?
4. @inletsdev 4
WE’VE RUN OUT OF IP ADDRESSES!
• 4 Billion IPv4 addresses
• Now completely sold out
• Time for IPv6?
340 trillion trillion trillion
addresses
25 years old already!
https://en.wikipedia.org/wiki/IPv4_address_exhaustion
5. @inletsdev 5
IPV4 VS. IPV6
IPv6
• Not widely available
• Some leaders -
Packet.com, ISPs: BT,
Kubernetes, Mythic Beasts
• Many laggards - hard to
upgrade completely
IPv4 work-arounds
• Time for a reality-check
• Carrier grade NAT (IP
sharing)
• Cloud vendors have stock-
piles
• Dual-stack for foreseeable
future
7. @inletsdev
REFRAMING THE PROBLEM
• CEO @ civo.com - IPs on
secondary market ~=20USD
• What if we could tap into the
stockpiles?
• 4 Billion addresses out there,
from 5 USD / mo
7