concept TCP load balancer in category kubernetes
appears as: TCP load balcer, TCP load balancer

This is an excerpt from Manning's book Core Kubernetes.
Take AWS service load balancing, for example. Sure, its easy enough to make a Service on an EC2 cluster with the
--type=LoadBalancerflag, but how would you add TLS to this Service? Is it secure? What happens if you delete this Service object - can you reuse the TCP load balancer? The code below is an example of the Service we just covered.apiVersion: v1 kind: Service metadata: labels: app: helloworld #1 name: helloworld spec: ports: - port: 8080 #2 protocol: TCP targetPort: 8888 selector: app: helloworld type: LoadBalancer #3 status: loadBalancer: ingress: - hostname: a54cae28bd42b11e7b2c7020a3f15370-27798109.eu-central-1.elb.amazonaws.comEven though Kubernetes magically added a TCP load balancer to the Status field after we created the preceding Service specification, a naive user might have a lot of work to do before integrating this Service into a production SaaS offering. The age-old questions of network security, routing, and TLS will never go away.