Task not finding API service

[RaikohGrass]

It is my first time managing an airflow deployment from the ground up in my AKS cluster. I am using the official helm charts and airflow 3.1.
Currently I already achieved having the UI up and ready to access through an ingress. After fetching a small dag from my github repo and trying to run it, it fails with the following error:

httpx.HTTPStatusError: Client error '403 Forbidden' for url 'https://my-cluster.westeurope.cloudapp.azure.com/airflow/execution/task-instances/0199e207-5656-7182-8f63-6a6e4b4a39ae/run'
For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403

That is when I set the api server url to my ingress:

execution_api_server_url: "https://my-cluster.westeurope.cloudapp.azure.com/airflow/execution/"

If I point it directly to the service instead I get a 404 for "/execution" but 200 for "api/v2/version".
From my understanding it seems that the executor is not being served by the api server?
I tried to set every option that I could find to make it available but to no avail. Am I missing something?

[RaikohGrass]

Got it to work after a while. Without ingress and forwarding the port to use the UI, the tasks were running fine. I checked the execution URL and it pointed per default to execution_api_server_url: "http://airflow-api-server:8080/execution/"
Adding the ingress again and overriding the execution URL with the subpath that I am using ( execution_api_server_url: "http://airflow-api-server:8080/airflow/execution/" ) the tasks run through 😉