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.

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

Clarifying what should happen when Gateway hostname is "" #525

Merged
merged 2 commits into from
Jan 12, 2021

Conversation

robscott
Copy link
Member

What type of PR is this?
/kind cleanup

What this PR does / why we need it:
We want this field to be optional as a pointer because it will be irrelevant for many protocols. That leaves us with three potential states, and this comment only covered two of them. Thanks to @yiyangy for finding this one!

Does this PR introduce a user-facing change?:

Clarifying that an empty Gateway hostname should be treated the same as an unspecified value.

Note: This is based on #519 since anything else will fail tests or result in an excessively large diff. Holding this PR until that merges. Please look at the second commit of this PR for the changes that are unique here.

/hold

This will prevent unnecessary changes and confusion each time we enter a
new year. This matches what other similar projects have already done.
We want this field to be optional as a pointer because it will be
irrelevant for many protocols. That leaves us with three potential
states, and this comment only covered two of them.
@k8s-ci-robot k8s-ci-robot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 12, 2021
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 12, 2021
@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 12, 2021
@hbagdi
Copy link
Contributor

hbagdi commented Jan 12, 2021

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 12, 2021
@hbagdi
Copy link
Contributor

hbagdi commented Jan 12, 2021

A rebase should get this merged in.

@robscott
Copy link
Member Author

Thanks!

/hold cancel

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jan 12, 2021
@k8s-ci-robot k8s-ci-robot merged commit a18491a into kubernetes-sigs:master Jan 12, 2021
@robscott robscott deleted the empty-hostname branch January 8, 2022 01:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants