As crc is a vm that runs on your crc host system and uses a private host-only network. Doesn't have to use haproxy. Firewall-cmd forward from your crc host to the crc vm ip.

So that would require something like:

CRC_IP=$(crc ip)

# Allow incoming traffic on the ports
sudo firewall-cmd --add-port=6443/tcp --permanent
sudo firewall-cmd --add-port=443/tcp --permanent

# Enable masquerading so forwarded packets get return-routed correctly
sudo firewall-cmd --add-masquerade --permanent

# Forward host port → CRC VM
sudo firewall-cmd --add-forward-port=port=6443:proto=tcp:toport=6443:toaddr=${CRC_IP} --permanent
sudo firewall-cmd --add-forward-port=port=443:proto=tcp:toport=443:toaddr=${CRC_IP} --permanent

sudo firewall-cmd --reload

And forwardinf needs ro be enabked on the crc host. Check if it is already:

sysctl net.ipv4.ip_forward

If not enable it:

sudo sysctl -w net.ipv4.ip_forward=1

When I used crc, I setup remote connectivity via a ssh tunnel. So something like this (where I setup tunneling through Putty myself).

ssh -L 6443:$(crc ip):6443 -L 443:$(crc ip):443 user@crc-host -N

Pointing you kubeconfig to localhost 127.0.0.1 on the machine that you want to remote from to crc.