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

Jump to bottom

Migrate Gateway API to k8s.io Group #2829

Closed
robscott opened this issue Jul 21, 2021 · 2 comments
Closed

Migrate Gateway API to k8s.io Group #2829

robscott opened this issue Jul 21, 2021 · 2 comments
Assignees
@robscott
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/network Categorizes an issue or PR as relevant to SIG Network.

Comments

@robscott
Copy link
Member

Enhancement Description

  • One-line enhancement description (can be used as a release note): Migrate Gateway API to k8s.io Group
  • Kubernetes Enhancement Proposal: WIP
  • Discussion Link: https://github.com/kubernetes-sigs/gateway-api
  • Primary contact (assignee): @robscott
  • Responsible SIGs: sig-network
  • Enhancement target (which target equals to which milestone): This is out of tree and will not be associated with any Kubernetes releases.

/sig network
/assign
@k8s-ci-robot k8s-ci-robot added the sig/network Categorizes an issue or PR as relevant to SIG Network. label Jul 21, 2021
@robscott robscott mentioned this issue Jul 21, 2021
Merged
@robscott robscott mentioned this issue Aug 13, 2021
Closed
@thockin thockin moved this from New, not evaluated to Pre-Alpha (we want to do this but the KEP or code is not merged yet) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Sep 2, 2021
This was referenced Sep 10, 2021
Closed
Closed
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 19, 2021
@robscott
Copy link
Member Author

I think this is accomplished now that we've released v1alpha2 in the k8s.io group. I'm not sure how much longer we need this issue, but may reopen it for beta.

/close

@thockin thockin removed this from Pre-Alpha (we want to do this but the KEP or code is not merged yet) in Obsolete: SIG-Network KEPs (see https://github.com/orgs/kubernetes/projects/148) Jan 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@robscott robscott

Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. sig/network Categorizes an issue or PR as relevant to SIG Network.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@robscott @k8s-ci-robot @k8s-triage-robot