Now we use a different set of openshift_login variables to login into the cluster depending of its flavor. For a full fledged OCP we typically use the kubeconfig file, the user, explicitly set to kubeadmin, and a path to the kubeadmin password file. For crc go with a mix of variables, depending of the environment file you look at.

The idea is to converge for both scenarios and always use the following:

• An existing kubeconfig file. From here oc will pickup the URL of the OCP cluster. Will be nice if we make both flavors to point to the same file. OCPs deployed with dev-scripts properly have the file in ~/.kube/config but the path for crc is ~/.crc/machines/crc/kubeconfig. Converging will be nice.
• The cifmw_openshift_user, set to kubeadmin
• The cifmw_openshift_password_file: Already exists in dev-scripts deployments and we only need to create it for crc with the already known password.