Question

How to expose k8s service to port 80 without a LoadBalancer

I have a basic kubernetes cluster with only one node and I want to add a domain to it. But for now I can only use the NodePort to expose the service. Is there a way to expose the service to port 80 without paying for additional LoadBalancer?


Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

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.

Yes, your option here would be to set you container as privileged and give it access to hostNetwork and use hostPort. I would not recommend this for any production workload as it relies on privileged containers and is advised against in the Kubernetes best practices.

I have provided a working example below:

apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: hostport
  name: hostport
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hostport
  template:
    metadata:
      labels:
        app: hostport
    spec:
      containers:
      - image: nginx:latest
        name: nginx
        securityContext:
          privileged: true
        ports:
          - name: http
            containerPort: 80
            hostPort: 80
      hostNetwork: true

You should then be able to access this deployment using:

curl <NODE_IP>:80

Note that because this is using the actual port of the host only the NODE_IP of a node running this pod will respond, unlike a nodeport service where traffic will be forwarded.

Hope this helps!

You can configure an ingress for the same. However, you will need a domain pointed to your k8s cluster or etchosts entry for cluster ips.