Adding NAT Gateway for Kubernetes
complete
B
Bikram Gupta
Routing agent is a built-in component in DOKS now. It supports egress configuration with multiple gateways (ECMP) and also supports setting up default (0.0.0.0) route.
https://docs.digitalocean.com/products/kubernetes/how-to/use-routing-agent/
It does require that you set up your own NAT gateway, which you may use one or more droplets. Managed NAT gateway is being actively worked on as part of the roadmap.
W
Whitney Jutzin
updated the status to
complete
Thank you for taking the time to share this helpful feedback with us. We now natively support Managed NAT Gateways. You can pair your cluster's built-in Routing Agent with a Managed NAT Gateway to centralize outbound internet traffic and achieve a static egress IP without needing to manage your own NAT Droplets: https://docs.digitalocean.com/products/kubernetes/how-to/use-routing-agent/ If you need any help getting this set up, please reach out to our support team: https://cloudsupport.digitalocean.com/ Thank you again!
B
Bikram Gupta
Routing agent is a built-in component in DOKS now. It supports egress configuration with multiple gateways (ECMP) and also supports setting up default (0.0.0.0) route.
It does require that you set up your own NAT gateway, which you may use one or more droplets. Managed NAT gateway is being actively worked on as part of the roadmap.
W
Whitney Jutzin
Thank you for reaching out to us with this insightful feedback. Our Product team is still investigating this product improvement. In the mean time, our team has this as a possible workaround: https://github.com/digitalocean/container-blueprints/tree/main/DOKS-Egress-Gateway This might help. If you need help implementing this, please reach out to our support team at https://cloudsupport.digitalocean.com/s/ Thank you again and we'll continue to update you as more information becomes available.
B
Bikram Gupta
Now that DOKS supports a built-in routing agent, we have deprecated the above blueprint.