José Castillo Lema
José Castillo Lema
Does the e2e cluster already support loadbalancer type services? If not, would it be possible/worth it to [install the MetalLB operator](https://docs.openshift.com/container-platform/4.10/networking/metallb/metallb-operator-install.html) on the e2e cluster in order to include loadbalancer...
Are those differences between rootful and rootles mode listed somewhere? Thanks!
Thanks for you quick response @BenTheElder ! Correct me if I am wrong but the restrictions listed on https://kind.sigs.k8s.io/docs/user/rootless/#restrictions correspond to docker, not to kind. While I totally get that...
Validated on scale lab: ``` [kni@f33-h17-000-r640 ~]$ oc get tigerastatus NAME AVAILABLE PROGRESSING DEGRADED SINCE apiserver True False False 48m calico True False False 22m ```
> Ah, now I see #219 opened separately, but the commit got included in this PR, too. Dropped #219 from this PR
https://github.com/redhat-performance/web-burner/blob/main/.github/workflows/ci.yml#L106
Removing https://github.com/redhat-performance/web-burner/blob/main/objectTemplates/pod_serving.yml#L6 works.
@vishnuchalla I think @rsevilla87 planned to keep this issue opened to track the medium term solution.
@gfauredev solution works! It is possible to configure it in the wezterm config file as well: ``` default_gui_startup_args = {'start', '--always-new-process'} ```
Thanks @rsulli55 the workaround works. However, is there a way to disable this `root_dir` requirement? The same folder without _.git_, _.opam_ files, etc. works fine on VSCode, however it does...