You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An ingress using ingress-nginx has already been set up correctly in the AKS cluster in the kernelci-api namespace. Then when I try to add another one for kernelci-pipeline to handle LAVA callbacks I get this error:
A temporary solution would be to run the callback handler on the staging VM for the early access phase, but this will need to be addressed properly for a full production deployment. One workaround would be to use a separate cluster for the pipeline, but it seems like there should be a way to properly set this up with multiple ingresses. Also, we ultimately won't need DNS labels if we just rely on the LF DNS for kernelci.org subdomains so that might simplify things a bit. We'll still needed multiple ingress definitions to route the traffic to either the API or a client-side service (LAVA callback, KCIDB bridge etc.).
The text was updated successfully, but these errors were encountered:
An ingress using
ingress-nginx
has already been set up correctly in the AKS cluster in thekernelci-api
namespace. Then when I try to add another one forkernelci-pipeline
to handle LAVA callbacks I get this error:As a result, I don't think we can set a different DNS label for the callback ingress:
A temporary solution would be to run the callback handler on the staging VM for the early access phase, but this will need to be addressed properly for a full production deployment. One workaround would be to use a separate cluster for the pipeline, but it seems like there should be a way to properly set this up with multiple ingresses. Also, we ultimately won't need DNS labels if we just rely on the LF DNS for
kernelci.org
subdomains so that might simplify things a bit. We'll still needed multiple ingress definitions to route the traffic to either the API or a client-side service (LAVA callback, KCIDB bridge etc.).The text was updated successfully, but these errors were encountered: