decision: Segmenting API Gateway features into PolicyAttachment CRDs #677
Description
Description:
Adding options for how API Gateway features such as ratelimiting can be expressed as PolicyAttachment CRDs. Please dont focus on the names, just added placeholders.
- one generic policy CRD with features as top level fields
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: Policy
.....
spec:
authentication:
.....
ratelimiting:
....
- one generic policy CRD with
networking(shapes traffic) andsecurity(authenticates & authorizes traffic) as top fields
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: Policy
.....
spec:
security:
authentication:
....
networking:
ratelimiting:
.....
- 2 Policy CRDs - one for
networkingand the other forsecurity
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: SecurityPolicy
....
....
spec:
authentication:
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: NetworkingPolicy
....
spec:
ratelimiting:
....
- 1 CRD per API Gateway feature
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: Authentication
....
spec:
jwt:
....
apiVersion: gateway.envoyproxy.io/v1alpha1
kind: Ratelimiting
....
spec:
....