This looks like an RBAC issue. When you ran the patch command after helm init did you get any output or errors? Ensure all the curly braces {} and single quotes are properly typed. Here is the command to help, after the paste ensure the single quotes are not changed to back-quotes:

It looks like a connection issue from helm to the kube-apiserver. If not RBAC then an issue with other authentication, or networking misconfiguration I would suspect. I have just run the steps as a regular student user, the same I used for the rest of the steps. I know the .kube/config file works that way. The lab works as expected, so the software hasn't broken (which can happen with dynamic projects).

This is most likely tied to a network issue if not RBAC nor having a proper config file. For example I see in your errors requests going to port 443, not 6443 which is where the API server listens.

Did all the previous commands work?
Have you been able to exec into a pod and run commands?
Are you running Calico, did you edit anything there?

What I would try next:
1) Run the lab as the non-root user I used for the rest of the labs.

2) Check that there are no firewalls on any of the nodes or between the nodes that would block traffic.

3) Were there any previous steps you did extra or not do to get here? Same OS, version, software used etc? Errors before this issue?

This problem happens when working with virtualbox based kubernetes.
I installed kubernetes on PC directly and there was not this problem.
Solution for Virtualbox based kubernetes is, to replace 192.168.0.0 in calico.yaml with 172.16.0.0/16 before initialize with kubeadm init, then run command kubeadm init --pod-network-cidr 172.16.0.0/16

also all confguration at home dir needed to clear which clears also all depndencies
and copy this changed calico.yaml to home before run command kubectl apply -f calico.yaml

If using VirtualBox please ensure that all the various network interfaces are set to allow all traffic. By default VirtualBox limits the traffic, which may be why you are not seeing the 192.168.0.0 traffic.