Modify the k8s deployment test so it can be optionally used to test deployment to real k8s

[dboreham]

Currently it uses kind.

[dboreham]

We need to do this:

1. Use machine to deploy a k3s host machine.
2. Extract the kubectl config file from the host machine.
3. Use that file to drive a deployment of the stack.
4. Test functionality as before.

[dboreham]

Our k3s install with machine doesn't set it up for remote access properly.

Needs the host name added to the SAN list.
https://www.google.com/search?q=how+to+connect+kubectl+remotely+to+k3s&oq=how+to+connect+kubectl+remotely+to+k3s

[dboreham]

ExecStart=/usr/local/bin/k3s \
    server \
        '--disable=traefik' \
        '--tls-san=test19.bpi.servesthe.world' \

[dboreham]

systemctl daemon-reload && systemctl restart k3s

[dboreham]

uv run stack init --deploy-to k8s --kube-config /home/david/projects/play/deploy-test/test19-k3s.yml --image-registry registry.digitalocean.com/stack-testing --stack todo --output /home/david/projects/play/deploy-test/todo-spec.yml --http-proxy-fqdn test-todo-1.bpi.servesthe.world --config REACT_APP_API_URL=https://test-todo-1.bpi.servesth
e.world/api/todos

[dboreham]

Need to stack manage push-images

[dboreham]

echo <YOUR_TOKEN> | docker login registry.digitalocean.com -u <YOUR_TOKEN> --password-stdin

[dboreham]

This is working now.