I'm currently seeing an image pull problem as well, fwiw.
Once you get past that, here's an alternative approach to using minikube profiles. This makes the us-east namespace an edge site, so you don't need to do the IP range stuff.
## General
sudo systemctl stop firewalld
## US East
export KUBECONFIG=$HOME/.kube/config-us-east
minikube start -p us-east
kubectl create namespace us-east
kubectl config set-context --current --namespace us-east
skupper init --edge
skupper connect $HOME/secret.yaml
kubectl create deployment hello-world-backend --image
quay.io/skupper/hello-world-backend kubectl expose deployment hello-world-backend --port 8080
kubectl annotate service hello-world-backend
skupper.io/proxy=http## EU North
export KUBECONFIG=$HOME/.kube/config-eu-north
minikube start -p eu-north
# In a distinct shell:
#
# minikube update-context -p eu-north
# minikube tunnel -p eu-north
kubectl create namespace eu-north
kubectl config set-context --current --namespace eu-north
skupper init
skupper connection-token $HOME/secret.yaml
kubectl create deployment hello-world-frontend --image
quay.io/skupper/hello-world-frontend kubectl expose deployment hello-world-frontend --port 8080 --type LoadBalancer
curl $(kubectl get service hello-world-frontend -o jsonpath='http://{.status.loadBalancer.ingress[0].ip}:8080/')