Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bump gatewayapi to 1.1.0-rc2 #3336

Merged
merged 16 commits into from
May 7, 2024
Merged

bump gatewayapi to 1.1.0-rc2 #3336

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
16 commits
Select commit Hold shift + click to select a range
4e0d14e
bump gatewayapi
zirain May 7, 2024
d505385
fix lint and test
zirain May 7, 2024
2146692
yaml-lint
zirain May 7, 2024
bcd1bf0
fix scheme
zirain May 7, 2024
e9f8964
lint
zirain May 7, 2024
6c70251
fix conformance test
zirain May 7, 2024
14f6d72
add apiextensionsv1 to scheme
zirain May 7, 2024
2868700
lint
zirain May 7, 2024
622be98
fix test
zirain May 7, 2024
4c10c4c
skip GatewayHTTPListenerIsolation
zirain May 7, 2024
b937081
fix e2e
zirain May 7, 2024
94de261
skip HTTPRouteBackendRequestHeaderModifier
zirain May 7, 2024
8e64b6a
fix e2e
zirain May 7, 2024
6d94be5
fix e2e
zirain May 7, 2024
9d7b945
yaml lint
zirain May 7, 2024
ada30eb
update api/extension_types.md
zirain May 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
2 changes: 1 addition & 1 deletion api/v1alpha1/backendtrafficpolicy_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ type BackendTrafficPolicySpec struct {
// is being attached to.
// This Policy and the TargetRef MUST be in the same namespace
// for this Policy to have effect and be applied to the Gateway.
TargetRef gwapiv1a2.PolicyTargetReferenceWithSectionName `json:"targetRef"`
TargetRef gwapiv1a2.LocalPolicyTargetReferenceWithSectionName `json:"targetRef"`

// RateLimit allows the user to limit the number of incoming requests
// to a predefined value based on attributes within the traffic flow.
Expand Down
2 changes: 1 addition & 1 deletion api/v1alpha1/clienttrafficpolicy_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ type ClientTrafficPolicySpec struct {
// This Policy and the TargetRef MUST be in the same namespace
// for this Policy to have effect and be applied to the Gateway.
// TargetRef
TargetRef gwapiv1a2.PolicyTargetReferenceWithSectionName `json:"targetRef"`
TargetRef gwapiv1a2.LocalPolicyTargetReferenceWithSectionName `json:"targetRef"`
// TcpKeepalive settings associated with the downstream client connection.
// If defined, sets SO_KEEPALIVE on the listener socket to enable TCP Keepalives.
// Disabled by default.
Expand Down
2 changes: 1 addition & 1 deletion api/v1alpha1/envoyextensionypolicy_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ type EnvoyExtensionPolicySpec struct {
// is being attached to.
// This Policy and the TargetRef MUST be in the same namespace
// for this Policy to have effect and be applied to the Gateway or xRoute.
TargetRef gwapiv1a2.PolicyTargetReferenceWithSectionName `json:"targetRef"`
TargetRef gwapiv1a2.LocalPolicyTargetReferenceWithSectionName `json:"targetRef"`

// Wasm is a list of Wasm extensions to be loaded by the Gateway.
// Order matters, as the extensions will be loaded in the order they are
Expand Down
4 changes: 2 additions & 2 deletions api/v1alpha1/envoypatchpolicy_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -49,12 +49,12 @@ type EnvoyPatchPolicySpec struct {
JSONPatches []EnvoyJSONPatchConfig `json:"jsonPatches,omitempty"`
// TargetRef is the name of the Gateway API resource this policy
// is being attached to.
// By default attaching to Gateway is supported and
// By default, attaching to Gateway is supported and
// when mergeGateways is enabled it should attach to GatewayClass.
// This Policy and the TargetRef MUST be in the same namespace
// for this Policy to have effect and be applied to the Gateway
// TargetRef
TargetRef gwapiv1a2.PolicyTargetReference `json:"targetRef"`
TargetRef gwapiv1a2.LocalPolicyTargetReference `json:"targetRef"`
// Priority of the EnvoyPatchPolicy.
// If multiple EnvoyPatchPolicies are applied to the same
// TargetRef, they will be applied in the ascending order of
Expand Down
2 changes: 1 addition & 1 deletion api/v1alpha1/securitypolicy_types.go
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ type SecurityPolicySpec struct {
// is being attached to.
// This Policy and the TargetRef MUST be in the same namespace
// for this Policy to have effect and be applied to the Gateway.
TargetRef gwapiv1a2.PolicyTargetReferenceWithSectionName `json:"targetRef"`
TargetRef gwapiv1a2.LocalPolicyTargetReferenceWithSectionName `json:"targetRef"`

// CORS defines the configuration for Cross-Origin Resource Sharing (CORS).
//
Expand Down
2 changes: 1 addition & 1 deletion api/v1alpha1/zz_generated.deepcopy.go
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

20,794 changes: 13,674 additions & 7,120 deletions charts/gateway-helm/crds/gatewayapi-crds.yaml
View file
Open in desktop

Large diffs are not rendered by default.

28 changes: 7 additions & 21 deletions charts/gateway-helm/crds/generated/gateway.envoyproxy.io_backendtrafficpolicies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -866,25 +866,16 @@ spec:
maxLength: 253
minLength: 1
type: string
namespace:
description: |-
Namespace is the namespace of the referent. When unspecified, the local
namespace is inferred. Even when policy targets a resource in a different
namespace, it MUST only apply to traffic originating from the same
namespace as the policy.
maxLength: 63
minLength: 1
pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
type: string
sectionName:
description: |-
SectionName is the name of a section within the target resource. When
unspecified, this targetRef targets the entire resource. In the following
resources, SectionName is interpreted as the following:


* Gateway: Listener Name
* Service: Port Name
* Gateway: Listener name
* HTTPRoute: HTTPRouteRule name
* Service: Port name


If a SectionName is specified, but does not exist on the targeted object,
Expand Down Expand Up @@ -1079,7 +1070,7 @@ spec:


* Gateway (Gateway conformance profile)
* Service (Mesh conformance profile, experimental, ClusterIP Services only)
* Service (Mesh conformance profile, ClusterIP Services only)


Support for other resources is Implementation-Specific.
Expand Down Expand Up @@ -1165,9 +1156,6 @@ spec:


Support: Extended


<gateway:experimental>
format: int32
maximum: 65535
minimum: 1
Expand All @@ -1178,14 +1166,12 @@ spec:
following resources, SectionName is interpreted as the following:


* Gateway: Listener Name. When both Port (experimental) and SectionName
* Gateway: Listener name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values.
* Service: Port Name. When both Port (experimental) and SectionName
* Service: Port name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values. Note that attaching Routes to Services as Parents
is part of experimental Mesh support and is not supported for any other
purpose.
both specified values.


Implementations MAY choose to support attaching Routes to other resources.
Expand Down
28 changes: 7 additions & 21 deletions charts/gateway-helm/crds/generated/gateway.envoyproxy.io_clienttrafficpolicies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -270,25 +270,16 @@ spec:
maxLength: 253
minLength: 1
type: string
namespace:
description: |-
Namespace is the namespace of the referent. When unspecified, the local
namespace is inferred. Even when policy targets a resource in a different
namespace, it MUST only apply to traffic originating from the same
namespace as the policy.
maxLength: 63
minLength: 1
pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
type: string
sectionName:
description: |-
SectionName is the name of a section within the target resource. When
unspecified, this targetRef targets the entire resource. In the following
resources, SectionName is interpreted as the following:


* Gateway: Listener Name
* Service: Port Name
* Gateway: Listener name
* HTTPRoute: HTTPRouteRule name
* Service: Port name


If a SectionName is specified, but does not exist on the targeted object,
Expand Down Expand Up @@ -639,7 +630,7 @@ spec:


* Gateway (Gateway conformance profile)
* Service (Mesh conformance profile, experimental, ClusterIP Services only)
* Service (Mesh conformance profile, ClusterIP Services only)


Support for other resources is Implementation-Specific.
Expand Down Expand Up @@ -725,9 +716,6 @@ spec:


Support: Extended


<gateway:experimental>
format: int32
maximum: 65535
minimum: 1
Expand All @@ -738,14 +726,12 @@ spec:
following resources, SectionName is interpreted as the following:


* Gateway: Listener Name. When both Port (experimental) and SectionName
* Gateway: Listener name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values.
* Service: Port Name. When both Port (experimental) and SectionName
* Service: Port name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values. Note that attaching Routes to Services as Parents
is part of experimental Mesh support and is not supported for any other
purpose.
both specified values.


Implementations MAY choose to support attaching Routes to other resources.
Expand Down
28 changes: 7 additions & 21 deletions charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoyextensionpolicies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -214,25 +214,16 @@ spec:
maxLength: 253
minLength: 1
type: string
namespace:
description: |-
Namespace is the namespace of the referent. When unspecified, the local
namespace is inferred. Even when policy targets a resource in a different
namespace, it MUST only apply to traffic originating from the same
namespace as the policy.
maxLength: 63
minLength: 1
pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
type: string
sectionName:
description: |-
SectionName is the name of a section within the target resource. When
unspecified, this targetRef targets the entire resource. In the following
resources, SectionName is interpreted as the following:


* Gateway: Listener Name
* Service: Port Name
* Gateway: Listener name
* HTTPRoute: HTTPRouteRule name
* Service: Port name


If a SectionName is specified, but does not exist on the targeted object,
Expand Down Expand Up @@ -510,7 +501,7 @@ spec:


* Gateway (Gateway conformance profile)
* Service (Mesh conformance profile, experimental, ClusterIP Services only)
* Service (Mesh conformance profile, ClusterIP Services only)


Support for other resources is Implementation-Specific.
Expand Down Expand Up @@ -596,9 +587,6 @@ spec:


Support: Extended


<gateway:experimental>
format: int32
maximum: 65535
minimum: 1
Expand All @@ -609,14 +597,12 @@ spec:
following resources, SectionName is interpreted as the following:


* Gateway: Listener Name. When both Port (experimental) and SectionName
* Gateway: Listener name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values.
* Service: Port Name. When both Port (experimental) and SectionName
* Service: Port name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values. Note that attaching Routes to Services as Parents
is part of experimental Mesh support and is not supported for any other
purpose.
both specified values.


Implementations MAY choose to support attaching Routes to other resources.
Expand Down
25 changes: 5 additions & 20 deletions charts/gateway-helm/crds/generated/gateway.envoyproxy.io_envoypatchpolicies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ spec:
description: |-
TargetRef is the name of the Gateway API resource this policy
is being attached to.
By default attaching to Gateway is supported and
By default, attaching to Gateway is supported and
when mergeGateways is enabled it should attach to GatewayClass.
This Policy and the TargetRef MUST be in the same namespace
for this Policy to have effect and be applied to the Gateway
Expand All @@ -146,16 +146,6 @@ spec:
maxLength: 253
minLength: 1
type: string
namespace:
description: |-
Namespace is the namespace of the referent. When unspecified, the local
namespace is inferred. Even when policy targets a resource in a different
namespace, it MUST only apply to traffic originating from the same
namespace as the policy.
maxLength: 63
minLength: 1
pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
type: string
required:
- group
- kind
Expand Down Expand Up @@ -278,7 +268,7 @@ spec:


* Gateway (Gateway conformance profile)
* Service (Mesh conformance profile, experimental, ClusterIP Services only)
* Service (Mesh conformance profile, ClusterIP Services only)


Support for other resources is Implementation-Specific.
Expand Down Expand Up @@ -364,9 +354,6 @@ spec:


Support: Extended


<gateway:experimental>
format: int32
maximum: 65535
minimum: 1
Expand All @@ -377,14 +364,12 @@ spec:
following resources, SectionName is interpreted as the following:


* Gateway: Listener Name. When both Port (experimental) and SectionName
* Gateway: Listener name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values.
* Service: Port Name. When both Port (experimental) and SectionName
* Service: Port name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values. Note that attaching Routes to Services as Parents
is part of experimental Mesh support and is not supported for any other
purpose.
both specified values.


Implementations MAY choose to support attaching Routes to other resources.
Expand Down
28 changes: 7 additions & 21 deletions charts/gateway-helm/crds/generated/gateway.envoyproxy.io_securitypolicies.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -697,25 +697,16 @@ spec:
maxLength: 253
minLength: 1
type: string
namespace:
description: |-
Namespace is the namespace of the referent. When unspecified, the local
namespace is inferred. Even when policy targets a resource in a different
namespace, it MUST only apply to traffic originating from the same
namespace as the policy.
maxLength: 63
minLength: 1
pattern: ^[a-z0-9]([-a-z0-9]*[a-z0-9])?$
type: string
sectionName:
description: |-
SectionName is the name of a section within the target resource. When
unspecified, this targetRef targets the entire resource. In the following
resources, SectionName is interpreted as the following:


* Gateway: Listener Name
* Service: Port Name
* Gateway: Listener name
* HTTPRoute: HTTPRouteRule name
* Service: Port name


If a SectionName is specified, but does not exist on the targeted object,
Expand Down Expand Up @@ -846,7 +837,7 @@ spec:


* Gateway (Gateway conformance profile)
* Service (Mesh conformance profile, experimental, ClusterIP Services only)
* Service (Mesh conformance profile, ClusterIP Services only)


Support for other resources is Implementation-Specific.
Expand Down Expand Up @@ -932,9 +923,6 @@ spec:


Support: Extended


<gateway:experimental>
format: int32
maximum: 65535
minimum: 1
Expand All @@ -945,14 +933,12 @@ spec:
following resources, SectionName is interpreted as the following:


* Gateway: Listener Name. When both Port (experimental) and SectionName
* Gateway: Listener name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values.
* Service: Port Name. When both Port (experimental) and SectionName
* Service: Port name. When both Port (experimental) and SectionName
are specified, the name and port of the selected listener must match
both specified values. Note that attaching Routes to Services as Parents
is part of experimental Mesh support and is not supported for any other
purpose.
both specified values.


Implementations MAY choose to support attaching Routes to other resources.
Expand Down
Loading
Loading