<p>I am using this yaml file for deployment - <a href="https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/master/deploy/single/all-in-one-dbless.yaml" rel="nofollow noreferrer">https://raw.githubusercontent.com/Kong/kubernetes-ingress-controller/master/deploy/single/all-in-one-dbless.yaml</a></p>
<p>I'm wondering if I can install Kong with type NodePort? My enterprise cloud isn't allowing me to create resource of type LoadBalancer.</p>

<p>Yes, you can do it, just change the service type to <strong>NodePort</strong>.</p>
<p>There is also thread discussion in Kong community : <a href="https://discuss.konghq.com/t/expose-kong-on-nodeport/8497" rel="nofollow noreferrer">https://discuss.konghq.com/t/expose-kong-on-nodeport/8497</a></p>
<pre><code>---
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:
  ports:
  - name: proxy
    port: 80
    protocol: TCP
    targetPort: 8000
  - name: proxy-ssl
    port: 443
    protocol: TCP
    targetPort: 8443
  selector:
    app: ingress-kong
  type: NodePort
---
</code></pre>
<p>You might need to take care of POD scheduling on the same node each time, with NodeSelector or affinity if using NodeIP as DNS somewhere in routing or so.</p>
<p>You can also check document of <strong>KIC</strong> in this doc : <a href="https://kind.sigs.k8s.io/docs/user/ingress/" rel="nofollow noreferrer">https://kind.sigs.k8s.io/docs/user/ingress/</a></p>
