How a Kubernetes bug won’t let you expose a service over TCP and UDP on a same port

How a Kubernetes bug won’t let you expose a service over TCP and UDP on a same port

  • March 3, 2019
Table of Contents

How a Kubernetes bug won’t let you expose a service over TCP and UDP on a same port

How I wasted hours of my life because of an unfixed 2016 Kubernetes’s bug that didn’t want me to expose a service over both UDP and TCP on a same port. Long story short, I wasted hours of my life because of an unfixed 2016 Kubernetes’s bug that didn’t want me to expose a service over both UDP and TCP on a same port. May this article come up in your Google search and save you hours of suffering.

Source: github.io

Tags :
Share :
comments powered by Disqus

Related Posts

Can Kubernetes Keep a Secret? It all depends what tool you’re using

Can Kubernetes Keep a Secret? It all depends what tool you’re using

Read More
Kubernetes network deep dive: Did you make the right choice?

Kubernetes network deep dive: Did you make the right choice?

Read More
Kubernetes Metrics and Monitoring

Kubernetes Metrics and Monitoring

This post explores the current state of metrics and monitoring in Kubernetes by walking through the gradual thought process that I experienced when learning this topic. Kubernetes needs some metrics for it’s basic out-of-the-box functionality, like autoscaling and scheduling. This is regardless of any monitoring solution you may want for the purpose of troubleshooting and alerting.

Read More