Description of problem: Creation of a new Route within a namespace that has multiple Services does not provide a mechanism for splitting the traffic across multiple Service endpoints with a weighting as was provided graphically in the 3.x console. Whilst this still can be achieved by handcrafting YAML it was a feature that customers liked, especially for Canary deployments of applications Version-Release number of selected component (if applicable): OCP4.1, K8S v1.13.4+838b4fa How reproducible: Always, option is missing from the Create Route dialog Steps to Reproduce: 1. Add two applications to a namespace (i.e. nodetest1, nodetest2) 2. Ensure that the nodetest1 and nodetest2 Service exist by going to Networking/Services on the OCP4.1 management console 3. Select Networking/Routes, Create Route Actual results: UI components allow for the creation of a Route with a single Service endpoint and no option to add an additional one with a network weighting for splitting traffic Expected results: OCP3.11 provides this graphical functionality. In the absence of the 4.2 Pipeline UI which I assume won't bring this back the 4.1 UI does not - you can handcraft YAML but that is not intuitive for existing customers of 3.x that use this feature Additional info:
4.3.0-0.nightly-2019-10-20-140322 Checked on OCP 4.3 with above payload version, now creating route with multiple services from form is available on console. The bug is fixed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062