Issues bootstrapping Juju into microk8s-on-AWS

I spun up an Ubuntu server, then ran sudo snap install microk8s --classic. I then ran microk8s.enable dns ingress storage, copied over the output from microk8s.config, and tried to import microk8s into Juju:

juju add-k8s uk8saws --controller uk8saws --region=aws/us-east-1 --storage juju-operator-storage

This failed first off due to security groups, and I had to run juju run --unit ubuntu/0 "open-port 16443" to open up the secure server port. I also ran juju expose ubuntu, but I’m not sure if that was also necessary in addition to the open-port command.

Next up was the issue of microk8s.config pointing at the internal IP address, and I had to manually edit the kubeconfig to point at the external IP address that I copied from the AWS console.

Finally, I had to manually edit /var/snap/microk8s/current/certs/csr.conf.template to add IP.3 = $PUBLIC_IP, and ran sudo snap restart microk8s. I still wasn’t able to get a connection, and looking at /var/snap/microk8s/current/certs/csr.conf.rendered showed that that line was actually getting overwritten, and I had to put IP.7 = $PUBLIC_IP, restart microk8s again, and then I was able to successfully import microk8s into juju.

Not sure if this is all just stuff that should have updated documentation, or if any of it should result in code changes, but opening this issue in case anyone else runs into the same issue.

[knkski]

@paravatha: Can you file a new issue with details about the sub-menu items you’re unable to access?

[sakaia]

@paravatha thank you for notification. I also uses kubectl port-forward and it seems work fine for jupyternotebook etc.