The instructions at https://skupper.io/start/minikube.html assume that when running minikube tunnel, the correct kubeconfig is set. If multiple separate profiles for minikube are run at once, then the tunnel can only be run for one of them. For the hello world example this would require tweaking the instructions such that the backend site connects to the frontend site (so that the frontend site can have loadbalancer capability as it uses that for the exposed service also). The backend site would need to use --cluster-local or --edge on skupper init.
Correction: I'm advised that you can have multiple tunnels by setting --service-cluster-ip-range on minikube start to have different ranges for the different profiles.
The instructions at https://skupper.io/start/minikube.html assume that when running minikube tunnel, the correct kubeconfig is set. If multiple separate profiles for minikube are run at once, then the tunnel can only be run for one of them. For the hello world example this would require tweaking the instructions such that the backend site connects to the frontend site (so that the frontend site can have loadbalancer capability as it uses that for the exposed service also). The backend site would need to use --cluster-local or --edge on skupper init.