Skip to content

Add design/20230601.gateway-route-hostnames.#6124

Merged
jetstack-bot merged 3 commits intocert-manager:masterfrom
tommie:route-design
Feb 18, 2024
Merged

Add design/20230601.gateway-route-hostnames.#6124
jetstack-bot merged 3 commits intocert-manager:masterfrom
tommie:route-design

Conversation

@tommie
Copy link
Copy Markdown
Contributor

@tommie tommie commented Jun 1, 2023

Pull Request Motivation

Discussed #6051 with @irbekrm, who suggested making a design doc.

Kind

design

Release Note

NONE

Signed-off-by: Tommie Gannert <tommie@gannert.se>
@jetstack-bot jetstack-bot added release-note-none Denotes a PR that doesn't merit a release note. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jun 1, 2023
@jetstack-bot
Copy link
Copy Markdown
Contributor

Hi @tommie. Thanks for your PR.

I'm waiting for a cert-manager member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

@jetstack-bot jetstack-bot added needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. kind/design Categorizes issue or PR as related to design. and removed needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jun 1, 2023
Co-authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: tommie <tommie@users.noreply.github.com>
@jetstack-bot
Copy link
Copy Markdown
Contributor

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle stale

@jetstack-bot jetstack-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Nov 13, 2023
@jetstack-bot
Copy link
Copy Markdown
Contributor

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to jetstack.
/lifecycle rotten
/remove-lifecycle stale

@jetstack-bot jetstack-bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Dec 13, 2023
@tommie
Copy link
Copy Markdown
Contributor Author

tommie commented Dec 14, 2023

@jsoref is anything missing here?

Copy link
Copy Markdown
Contributor

@jsoref jsoref left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems fine to me (with these changes), but, I'd rather someone else approve...

@jetstack-bot
Copy link
Copy Markdown
Contributor

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

@jetstack-bot
Copy link
Copy Markdown
Contributor

@jetstack-bot: Closed this PR.

Details

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to jetstack.
/close

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.

@inteon
Copy link
Copy Markdown
Member

inteon commented Jan 29, 2024

/remove-lifecycle rotten
/reopen

@jetstack-bot jetstack-bot reopened this Jan 29, 2024
@jetstack-bot
Copy link
Copy Markdown
Contributor

@inteon: Reopened this PR.

Details

In response to this:

/remove-lifecycle rotten
/reopen

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.

@jetstack-bot jetstack-bot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Jan 29, 2024
Copy link
Copy Markdown
Member

@inteon inteon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like the design, I think it makes a lot of sense and will improve the experience for users of GatewayAPI. This has become even more important now that GatewayAPI v1 has been released.

/lgtm
/approve
/hold for other reviews/ @jsoref's changes to be added

@jetstack-bot jetstack-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm Indicates that a PR is ready to be merged. labels Feb 6, 2024
@jetstack-bot
Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@jetstack-bot jetstack-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 6, 2024
@tommie
Copy link
Copy Markdown
Contributor Author

tommie commented Feb 6, 2024

@inteon Thank you. I'll get to the review comments shortly.

Co-authored-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
Signed-off-by: tommie <tommie@users.noreply.github.com>
@jetstack-bot jetstack-bot removed the lgtm Indicates that a PR is ready to be merged. label Feb 18, 2024
@tommie
Copy link
Copy Markdown
Contributor Author

tommie commented Feb 18, 2024

@inteon Suggestions applied.

@inteon
Copy link
Copy Markdown
Member

inteon commented Feb 18, 2024

Thank you very much!
This will be a great help to all contributors working on implementing this feature in the future ❤️.
/unhold
/lgtm

@jetstack-bot jetstack-bot added lgtm Indicates that a PR is ready to be merged. and removed do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Feb 18, 2024
@jetstack-bot jetstack-bot merged commit 8ea586e into cert-manager:master Feb 18, 2024
@ljhlh49-dot
Copy link
Copy Markdown

Pull Request Motivation

Discussed #6051 with @irbekrm, who suggested making a design doc.

Kind

design

Release Note


NONE

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. dco-signoff: yes Indicates that all commits in the pull request have the valid DCO sign-off message. kind/design Categorizes issue or PR as related to design. lgtm Indicates that a PR is ready to be merged. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. release-note-none Denotes a PR that doesn't merit a release note. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants