-
Notifications
You must be signed in to change notification settings - Fork 472
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.
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
Clarify BackendObjectReference Port field godoc #1332
Clarify BackendObjectReference Port field godoc #1332
Conversation
Hi @Miciah. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@@ -123,7 +123,8 @@ type BackendObjectReference struct { | |||
Namespace *Namespace `json:"namespace,omitempty"` | |||
|
|||
// Port specifies the destination port number to use for this resource. | |||
// Port is required when the referent is a Kubernetes Service. | |||
// Port is required when the referent is a Kubernetes Service. In this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
// Port is required when the referent is a Kubernetes Service. In this | |
// Port is required when the referent is a Kubernetes Service. In this |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated (though it pains me to use single sentence spacing; 💔).
Thanks @Miciah! This change LGTM, do you mind mirroring this to the v1alpha2 types file as well? |
/ok-to-test |
* apis/v1alpha2/object_reference_types.go (BackendObjectReference): * apis/v1beta1/object_reference_types.go (BackendObjectReference): Clarify that the Port field references the service port number when the backend is a Kubernetes Service. * config/crd/experimental/gateway.networking.k8s.io_grpcroutes.yaml: * config/crd/experimental/gateway.networking.k8s.io_httproutes.yaml: * config/crd/experimental/gateway.networking.k8s.io_tcproutes.yaml: * config/crd/experimental/gateway.networking.k8s.io_tlsroutes.yaml: * config/crd/experimental/gateway.networking.k8s.io_udproutes.yaml: * config/crd/standard/gateway.networking.k8s.io_httproutes.yaml: Regenerate.
37f64ab
to
82ebeaf
Compare
Done. |
Thanks @Miciah! /lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Miciah, robscott The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
apis/v1alpha2/object_reference_types.go
(BackendObjectReference
):apis/v1beta1/object_reference_types.go
(BackendObjectReference
): Clarify that thePort
field references the service port number when the backend is a Kubernetes Service.config/crd/experimental/gateway.networking.k8s.io_grpcroutes.yaml
:config/crd/experimental/gateway.networking.k8s.io_httproutes.yaml
:config/crd/experimental/gateway.networking.k8s.io_tcproutes.yaml
:config/crd/experimental/gateway.networking.k8s.io_tlsroutes.yaml
:config/crd/experimental/gateway.networking.k8s.io_udproutes.yaml
:config/crd/standard/gateway.networking.k8s.io_httproutes.yaml
: Regenerate.What type of PR is this?
/kind documentation
What this PR does / why we need it:
Clarify that
BackendObjectReference
'sPort
field specifies a service port, not a target port, when the backend is a Kubernetes Service.Which issue(s) this PR fixes:
Fixes #1331.
Does this PR introduce a user-facing change?: