minikube on aws docs update
@@ -459,6 +459,7 @@ Create and modify qhub-config.yaml:
mkdir data-test
cd data-test
+export QHUB_GH_BRANCH=main
qhub init local --project=thisisatest --domain github-actions.qhub.dev --auth-provider=password
sed -i -E 's/(cpu_guarantee):\s+[0-9\.]+/\1: 1/g' "qhub-config.yaml"
@@ -524,7 +525,7 @@ EOF
Now SSH into the AWS instance, enabling port forwarding so you can access the Minikube cluster as though it is running on your Mac:
```bash
-ssh -i ~/.ssh/aws-quansight-dsl.pem ubuntu@ec2-18-130-21-222.eu-west-2.compute.amazonaws.com -L 127.0.0.1:8443:192.168.49.2:8443
+ssh -i ~/.ssh/aws-quansight-mykey.pem ubuntu@ec2-18-130-21-222.eu-west-2.compute.amazonaws.com -L 127.0.0.1:8443:192.168.49.2:8443
```
You should now find that `kubectl` and `k9s` work for the Minikube cluster if you run them on your Mac! This can include `kubectl port-forward` to access Kubernetes services individually.
@@ -542,7 +543,7 @@ We can trick it by setting up a hostname alias. Run `sudo vi /etc/hosts` on the
And then we add an extra port forward when we SSH into the AWS instance:
```bash
-sudo ssh -i ~/.ssh/aws-quansight-dsl.pem ubuntu@ec2-35-177-109-173.eu-west-2.compute.amazonaws.com -L 127.0.0.1:8443:192.168.49.2:443 -L github-actions.qhub.dev:443:192.168.49.100:443
+sudo ssh -i ~/.ssh/aws-quansight-mykey.pem ubuntu@ec2-35-177-109-173.eu-west-2.compute.amazonaws.com -L 127.0.0.1:8443:192.168.49.2:8443 -L github-actions.qhub.dev:443:192.168.49.100:443
```
This has to be run with sudo because we want to forward a low-numbered port (443) and this is not allowed without sudo.
