search

lippertmarkus / helm-charts

11 stars 6 forks source link

How to access BC via public IP? #4

Closed staedter closed 2 years ago

staedter commented 3 years ago

Hi Markus,

I now got the rancher cluster running and sucessfully starting the helm chart but I do not really understand how to access the Business Central Instance over the public ip. I started the deployment a second time and a currently waiting for the node to finish pulling the image but I think the port-forwarding will not help me either, correct? image

I looked at your docu on artifacthub but I do not really know which of the 4 options is the best/correct one for my current usecase (which is just simply accessing 1 BC Instance hosted in k8s via the public IP) image I do not think that I really need the load balancer for this... Is ingress maybe the best route to go? And could you point me to some ressources that would explain to me how to set it up in Rancher?

Or am I on the wrong tract entirely?

Best regards Chris

lippertmarkus commented 3 years ago

Hey Chris,

for easily getting started you can try NodePort by adding --set service.type=NodePort to helm install. You can then get the node port via kubectl get svc. Make sure that this port is allowed in your firewall(s) and you can access it on http://public-ip:nodeport/BC

For a production setup you may rather want to use ingress. This basically gives you one entry point and can route to many Business Central containers. I suggest reading through the ingress docs as this setup is a bit more complex: https://kubernetes.io/docs/concepts/services-networking/ingress/

lippertmarkus commented 2 years ago

Closing this, feel free to reopen if you need more input