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.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.
Click below to sign up and get $200 of credit to try our products over 60 days!