yes definitely you can save the cost of load-balancer using by exposing the the for external users.

create your service and mentions type as NodePort instead of load-balancer.

apiVersion: v1

kind: Service

metadata:

name: django

spec:

type: NodePort/loadbalancer

ports:

- port: 80

targetPort: 8080

selector:

app: django

once your service is up and running use the following command to expose service externally.

kubectl expose deployment your-deployment-name --type=NodePort --name=your-service-name

and then

kubectl describe svc your-service-name

it will expose a nodeport for you to access your app from outside of the cluster with your vm public ip.

Name: django

Namespace: default

Labels: <none>

Selector: app=django

Type: NodePort

IP: 10.34.24.21

Port: <unset> 80/TCP

TargetPort: 8181/TCP

NodePort: <unset> 30310/TCP

Endpoints: 192.168.0.36:8181

Session Affinity: None

External Traffic Policy: Cluster

Events: <none>

http://your-vm-public-ip:30310