OSDU Provisioning Has Pods Perpetually In CrashLoopBackoff
I am trying to set up a developer instance of the OSDU to investigate how we would go about using it within my organisation. After several attempts at provisioning various different Helm charts following instructions on the OSDU git our team managed to get an instance running using docker desktop, however it seems very prone to falling over with some pods never getting out of a CrashLoopBackOff cycle. Below is the instructions we have developed for getting as far as we have:
Subsequently I have commissioned a VM with 64GB of memory (and allocated 50GB to the WSL) in case a lack of resources on the 32GB version referenced in the instructions was causing the issue, however the same problems seem to be presenting themselves.