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

Share :
comments powered by Disqus

Related Posts

Kubernetes Operations: Prioritize Workload in Overcommitted Clusters

Kubernetes Operations: Prioritize Workload in Overcommitted Clusters

One of the benefits in adopting a system like Kubernetes is facilitating burst-able and scalable workload. Horizontal application scaling involves adding or removing instances of an application to match demand. Kubernetes Horizontal Pod Autoscaler enables automated pod scaling based on demand.

Read More