Ingress not working on AWS.

I have a single node setup on AWS ubuntu instance using microk8s with ingress controller enabled by using microk8s.enable ingress. Which has added the following service:

NAME                   TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)   AGE
default-http-backend   ClusterIP   10.152.183.50   <none>        80/TCP    8m47s

and the following deployment:

NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
default-http-backend   1         1         1            1           10m

which I belive is the ingress controller.

Now when I try to create the following ingress:

---
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: basic-ingress
spec:
  backend:
    serviceName: nodeserver
    servicePort: 7070

The ADDRESS is not assigned to the ingress

kubectl get ingress
NAME            HOSTS   ADDRESS   PORTS   AGE
basic-ingress   *                 80      12m

Is there anything specific to AWS loadbalancers that needs to be configured? Or anything that I am missing in the configuration?

I tried installing nginx ingress controller saperately but same issue with that.

[ktsakalozos]

Currently, there is no integration with AWS (or any other cloud provider). You will need to create any loadbalancers manually.

This is an interesting feature we might consider implementing in the future. Thank you for the suggestion.

[AdamIsrael]

I am +1 to seeing this added as a feature. As we use microk8s in different ways, it’s becoming clear that we need to be able to use it more robustly. For example, I spin up a VM in a cloud and use microk8s for development, or a demo. I want to be able to expose an endpoint and poke at it outside of the machine.