<p>I must be able to disable a Kubernetes ingress at any point, and put it back on as easily. Is there a way to have a kind of &quot;feature switch&quot; to enable/disable an ingress at any moment, to stop forwarding traffic to the backend it's pointing to, and let us turn it on again?</p>

David Gourde
<p>I believe that what you are trying to achieve can be solved with <a href="https://istio.io/latest/docs/concepts/what-is-istio/" rel="nofollow noreferrer">Istio</a> (I'm not familiar with other Service Mesh, but I think you can do the same with them as well).</p>
<p>If you take a look at <a href="https://istio.io/latest/docs/examples/bookinfo/" rel="nofollow noreferrer">this example</a>, they deploy an app which has 3 different product review pages, and then using <a href="https://istio.io/latest/docs/concepts/traffic-management/#routing-rule-precedence" rel="nofollow noreferrer">Traffic Management - Routing Rules</a> they specify how the traffic will be handled in this product review page.</p>
<p>In the doc they go through some cases like round robin, percentage and user. So you could use the percentage to be your switch.</p>
<p>Lets say that you have backend v1 and v2, you could use traffic management to direct 100% of your requests to v1, change it to v2, and then change to v1 again, as much as you like.</p>
<p>You could also do something like 85% - 15%, and test your new backend just with a small percentage of your requests, evaluate and make the decision to move on, or roll back afterwards.</p>
