Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

By muffinista
I have a DO Load Balancer connecting to a kubernetes service with 3 ports: 80, 443, and port 70 (aka gopher). Here’s the definition:
metadata:
name: gopher-thingy
annotations:
service.beta.kubernetes.io/do-loadbalancer-protocol: "http"
service.beta.kubernetes.io/do-loadbalancer-algorithm: "round_robin"
service.beta.kubernetes.io/do-loadbalancer-tls-ports: "443"
service.beta.kubernetes.io/do-loadbalancer-certificate-id: "**redacted**"
spec:
type: LoadBalancer
ports:
- name: gopher
port: 70
targetPort: 70
protocol: TCP
- name: http
port: 80
targetPort: 80
protocol: TCP
- name: https
port: 443
targetPort: 80
protocol: TCP
I’ve exposed port 70 via a separate ConfigMap as described in the ingress setup docs
apiVersion: v1
kind: ConfigMap
metadata:
name: tcp-services
namespace: default
data:
70: "gopher-thingy:70"
When I apply this, HTTP and HTTPS are setup as expected, but the gopher port is forwarded to port 80 instead of port 70. I need to go into the load balancer in the networking panel and change it manually.
Am I missing something? This seems like a bug.
Thanks!
1a3ca91ed97c49039b3e74fb7229fa
6efbf601fa8e49c884398e706c4672
f27857d3fd85405b8f50d9997c684d
petercorrea
ulope
josaf bodia
jediD83
rafaelri
Lucas Souza
Ben Buzbee
andreasAngler