I was able to deploy the denodo 8 container on the kubernetes by following the steps given in the knowledge base article [Deploying Denodo in kubernetes](https://community.denodo.com/kb/view/document/Deploying%20Denodo%20in%20Kubernetes?category=Operation).
The error “CrashLoopBackOff” will occur when a pod is starting, crashing, and starting again and then crashing again. Since the pod is unstable at this stage we can't verify the exact reason why the pod is crashing by verifying the vdp.log file. In such a case,i would modify the YAML scripts to redirect the denodo logs folder(/opt/denodo/logs/vdp) from the container to the host path(/C/Denodo/Kubernetes/logs) to check for what reason the pod is crashing and fix the issue reported in the log file.
After reviewing your output of the “kubectl log” command, I would suggest you check if the licencing file path given in the YAML script is valid or not. Because I was able to reproduce the same error when trying with the invalid licence path in the YAML script during the creation of the container.
If you still need help and if you are a user with valid support access then you can raise a support case in [Denodo Support Site](https://support.denodo.com/) so that our support team can help you.
Hope this helps!