Comment 20 for bug 2032783

Alright, it looks better now, I added the IP range 10.152.183.0/24 to no_proxy variable, I didn't have to run the juju command manually. Now the pods get created successfully:

root@sunbeam:~# kubectl get pods -A
NAMESPACE NAME READY STATUS RESTARTS AGE
kube-system hostpath-provisioner-7df77bc496-sksdg 1/1 Running 0 117s
kube-system coredns-864597b5fd-8xgs4 1/1 Running 0 3m43s
metallb-system speaker-vvnfm 1/1 Running 0 115s
kube-system calico-node-xfhqc 1/1 Running 0 3m43s
metallb-system controller-5f7bb57799-cchdf 1/1 Running 0 115s
kube-system calico-kube-controllers-77bd7c5b-k9wjq 1/1 Running 0 3m43s

⠏ Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (0/24)

This takes some time (as expected), but after around 35 minutes, the bootstrap is complete and all pods are running. I'm going to configure it now.
One thing I can't really grasp is if the prepar script adds the ClusterIP to the no_proxy variable, I found it in the /etc/environment. But in the previous attempt it wasn't applied, at least that's how it seems to me. So there are still a couple of questions, but it seems to work in general.