Julien Gebelin (Customer) asked a question.

Ingress Controller installation issue

Hello,

 

For the context, i'm trying to setup loadmaster as my ingress controller for external adresses in my K8s cluster.

I created an ingress ressource with the following annotations:

  annotations:

    kemp.ax/vsip: "xx.xx.xx.xx"  

    kemp.ax/vsport: "xxx"      

    kemp.ax/vsprot: "tcp"

 

The guide provided doesn't have an up-to-date definition of the ingress configuration YAML and it doesn't have any ingressclass defined so its using my default one, which is nginx.

 

I installed my cluster kubeconfig in the Kubernetes Setting, my namespace populate the namespace to watch scrolldown, but no ingresses appears.

 

An other issue that may happens is that the gateway network of my nodes is not the same network my loadmaster is in, but both network can communicate with each other.

 

Do i need to setup an interface specifically in the same network?


  • Andrew Spagnuolo (Progress Software)

    Hi Julien,

     

    The LoadMaster does not necessarily need an interface on the same subnet as your Kubernetes nodes as long as routing exists.

     

    However it must be able to:

    • Reach your Kubernetes pod/node network
    • Route traffic back and forth properly
    • Have return traffic come back through correct gateway

     

    The nginx ingress class you have defined could also be an issue, perhaps its not recognizing it. Have you tried defining a different class name. For example our setup guide defines this as "kempLB" https://kemptechnologies.com/blog/kemp-ingress-controller-explained

     

    Best Regards,

    Selected as Best
  • Andrew Spagnuolo (Progress Software)

    Hi Julien,

     

    The LoadMaster does not necessarily need an interface on the same subnet as your Kubernetes nodes as long as routing exists.

     

    However it must be able to:

    • Reach your Kubernetes pod/node network
    • Route traffic back and forth properly
    • Have return traffic come back through correct gateway

     

    The nginx ingress class you have defined could also be an issue, perhaps its not recognizing it. Have you tried defining a different class name. For example our setup guide defines this as "kempLB" https://kemptechnologies.com/blog/kemp-ingress-controller-explained

     

    Best Regards,

    Selected as Best
  • Slawomir Jach (Customer)

    I think is time to move to gateway Api , I'm pretty sure it will solve lot of yours problems