Log in to your Inductive Automation account to give feedback
Configurable Context Path for Ignition
I'm aware of the proxy architecture, however the proxy doesn't help where the Ignition container is deploy/running. A proxy will allow for this: [Due to restricts of this forum, I can only put at the most 2 URLs in a post, so in the following scenario replace the _ with a dot .] proxy_com/ignition1 |---> ignition1_abc_com (deployed on Kubernetes cluster1) proxy_com/ignition2 |---> ignition2_abc_com (deployed on Kubernetes cluster2) You can't deploy more than 1 instances of Ignition on a Kubernetes clusters because all of the code currently depends on having the root context path (/). My goal is to have a proxy be able to route traffic to 2 (or more) instances of Ignition deployed to the same cluster: proxy_com/ignition1 |---> ignition_abc_com/ignition1 (deployed on Kubernetes cluster1) proxy_com/ignition2 |---> ignition_abc_com/ignition2 (deployed on Kubernetes cluster1) It doesn't make sense that I would need to create a new Kubernetes cluster each time I wanted to deploy an instance of Ignition. If the Kubernetes cluster has enough resources (CPU & Memory) it should be able to run as many instances of Ignition as we want. The root issue is that Ignition's links and redirects in the JavaScript are hardcoded to use the base context path of '/' and if there was just a way to pass in a variable as part of the Docker Build, that would be enough but I think this change would need implemented in the code base of Ignition as well. I did notice that at least part of the application uses a web.xml to handle some internal routes, it would be nice to have the ability to pass in a context root to that. Allowing for more flexibility to implement the product in the way the customer wants or needs.
Load More