Allow an implementation to use listed order for HTTPRouteFilter in a route-rule (#2687)

* Allow an implementation to use listed order for HTTPRouteFilter in a route-rule

* ran 'make generate' to regenerate the modified resurce definitions

* Specify stricter mode with "SHOULD" using the RFC 2119 definition

Co-authored-by: Rob Scott <[email protected]>

* use MUST instead of should for RFC2119 and remove extra spaces

* ran 'make generate' to regenerate the CRDs

* Change "in only" to "if only"

Co-authored-by: Rob Scott <[email protected]>

* Change "(s)" to "s"

Co-authored-by: Rob Scott <[email protected]>

* commit regenerated CRDs/comments

---------

Co-authored-by: Rob Scott <[email protected]>

Author: sanjaypujare

apis/v1/httproute_types.go

@@ -196,8 +196,19 @@ type HTTPRouteRule struct {
 	// Filters define the filters that are applied to requests that match
 	// this rule.
 	//
-	// The effects of ordering of multiple behaviors are currently unspecified.
-	// This can change in the future based on feedback during the alpha stage.
+	// Wherever possible, implementations SHOULD implement filters in the order
+	// they are specified.
+	//
+	// Implementations MAY choose to implement this ordering strictly, rejecting
+	// any combination or order of filters that can not be supported. If implementations
+	// choose a strict interpretation of filter ordering, they MUST clearly document
+	// that behavior.
+	//
+	// To reject an invalid combination or order of filters, implementations SHOULD
+	// consider the Route Rules with this configuration invalid. If all Route Rules
+	// in a Route are invalid, the entire Route would be considered invalid. If only
+	// a portion of Route Rules are invalid, implementations MUST set the
+	// "PartiallyInvalid" condition for the Route.
 	//
 	// Conformance-levels at this level are defined based on the type of filter:
 	//