Azure Kubernetes Service: Helm Chart w/ External Port

[ifTaylor]

Actions before raising this issue

• I searched the existing issues and did not find anything similar.
• I read/searched the docs

Is your feature request related to a problem? Please describe.

I'm not able to access the application from a service with an external port. I have deployed the cluster to an Azure Kubernetes Service by setting the cluster subscription, downloading cluster credentials, and following the deployment process. I am not able to attribute the nginx external loadbalancer IP that ASK provides within the values.override.yaml. Services are running, but I am not able to access the application.

Describe the solution you'd like

1. Provide a LoadBalancer service.
2. Help attributing the AKS nginx external IP.

Describe alternatives you've considered

docker-compose up -d using the docker-compose.yaml works flawlessly. I tried to convert the file using kompose, but was not able to get that working either.

Additional context

No response

[ifTaylor]

As I'm investigating this further, I've found the deployment command, helm upgrade -n cvat latest -i --create-namespace ./ -f ./values.yaml -f ./values.override.yaml, at the helm-chart level does not populate the traifik service.

I retraced my steps with setting up with Minikube and found when connecting to my AKS the command, helm install helm-chart helm-chart/ --replace, does populate the traefik service.

Although the traefik load balancer is present in Azure with an external ip, I am returning 404. I am not sure if this is due to the command not using the values.override.yaml file, or an Azure ingress needs to be set up separately. When setting up with Minikube, the traefik external ip still returns 404.

traefik:
  service:
    externalIPs:
      - "<minikube ip> OR <some Azure ip that I am missing>"

***edit:
Also in values.yaml I set ingress:endable: true and traefik:enabled: true.