Allow good config to be accepted even when other config is broken

[jameshbarton]

Version

1.13.x (latest stable)

Is your feature request related to a problem? Please describe.

An enterprise customer wants to allow good RouteTable config to be accepted even when another RouteTable containing bad config is present.

Use Case: There are multiple application teams. Team X has a broken RT, say due to missing headers. Team A is then unable to push good RouteTable updates specific to their services to the same proxy. We don't want Team A to be impacted by Team X's config problems.

Describe the solution you'd like

Allow good RouteTable config to be accepted even when another RouteTable containing bad config is present. Also, existing routes should keep working.

Describe alternatives you've considered

We've recommended more thorough pre-production testing to prevent the introduction of bad config. However, sometimes bad changes still make it through.

Additional Context

Internal Slack: https://solo-io-corp.slack.com/archives/C04A26WSZ43/p1678823716787709

Related Issues:

• https://github.com/solo-io/gloo/issues/8412
• https://github.com/solo-io/gloo/issues/6115