I am using minikube and Helm. I want to install odoo from this repo: https://artifacthub.io/packages/helm/bitnami/odoo
So far I have run the following command according to the documentation: helm install my-release oci://registry-1.docker.io/bitnamicharts/odoo
Everything seems to work well (except for some warnings: see below)
Now how do I access the app from my browser (i.e. through which ip:port)?
I have tried many combinations of ip:port
-
I first tried the command
kubectl get all, then looked at the lineservice/my-release-odoofrom where I took the ip and port and put it into the browser. But nothing shows up (This site can’t be reached). -
I have also tried to run
minikube ip(as suggested somewhere else) and use the output IP with a combination of many ports like 8069, 30300, or the one shown in step 1 above. Still, nothing shows up.
I am a starter on Kubernetes DevOps and I may miss something but I don’t know.
Warnings after install command:
WARNING: There are “resources” sections in the chart not set. Using “resourcesPreset” is not recommended for production. For production installations, please set the following values according to your workload needs:
- resources
+info https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/`
Warnings after running command minikube ip:
W0612 18:39:14.957390 2960 main.go:291] Unable to resolve the current Docker CLI context “default”: context “default”: context not found: open C:Usershp.dockercontextsmeta37a8eec1ce19687d132fe29051dca629d164e2c4958ba141d5f4133a33f0688fmeta.json: The system cannot find the path specified.
192.168.49.2
Short answer: Run the command I found here and paste the resulting URL in your browser.
Long answer:
The IP you are getting from the kubectl get all command is internal to the minikube cluster. You will not be able to access that one from your web browser. You must expose the odoo service first. You can do this by running a similar command to this one kubectl expose service/my-release-odoo --type="NodePort" --port 8080. Then you should be able to go to http://<your-vm-ip>:8080. You may have to go to http://<your-vm-ip>:8080 instead and bypass the unknown certificate error if you have not installed the certificate in your system’s trust store.