-
Hi everybody! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi @hesmoh 👋, When using a cloud provider the |
Beta Was this translation helpful? Give feedback.
-
We're using metal lb in some environments (not aws), and this config worked out of the box. - apiVersion: v1
kind: Service
metadata:
annotations:
service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
service.beta.kubernetes.io/aws-load-balancer-type: nlb
name: kong-proxy
namespace: kong
spec:
type: LoadBalancer
externalTrafficPolicy: Local
selector:
app: ingress-kong
ports:
- name: proxy
port: 80
protocol: TCP
targetPort: 8000
- name: proxy-ssl
port: 443
protocol: TCP
targetPort: 84 |
Beta Was this translation helpful? Give feedback.
Hi @hesmoh 👋,
When using a cloud provider the
LoadBalancer
type forServices
will be managed and provisioned by the environment (see https://kubernetes.io/docs/tasks/access-application-cluster/create-external-load-balancer/#external-load-balancer-providers) automatically, but when creating your own baremetal cluster you will need to add the service which will manage provisioning IPs forLoadBalancer
typeServices
. One such service is Metal-LB which is purpose built for this. Alternatively, you can use aNodePort
typeService
instead, and in fact our Helm Chart provides some options for deploying the ingress controller withNodePort
instead ofLoadBalancer
typeServices
.