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

Jump to bottom

GEP: Inherited Policy Attachment #2649

Open
youngnick opened this issue Dec 6, 2023 · 2 comments
Open

GEP: Inherited Policy Attachment #2649

youngnick opened this issue Dec 6, 2023 · 2 comments
Assignees
@youngnick
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@youngnick
Copy link
Contributor

Split out of #713.

This GEP covers work to define and implement an example Inherited Policy.

This includes at a minimum:

  • defining what makes an Inherited Policy
  • suggested patterns for ensuring discoverable status

Graduation criteria will be something like:

  • At least one included Inherited Policy
  • Included Policy must have conformance tests
  • Included Policy may be Extended support (and so, optional).
@youngnick youngnick added the kind/feature Categorizes issue or PR as related to a new feature. label Dec 6, 2023
@youngnick youngnick mentioned this issue Dec 6, 2023
Open
@guicassolato guicassolato mentioned this issue Jan 9, 2024
Merged
@mikemorris mikemorris mentioned this issue Jan 30, 2024
Closed
@youngnick youngnick mentioned this issue Feb 26, 2024
Merged
@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue 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 Mar 5, 2024
@youngnick
Copy link
Contributor Author

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Mar 6, 2024
@youngnick youngnick self-assigned this Mar 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@youngnick youngnick

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
Gateway API Enhancement Proposals (GEPs)
Status: Proposed
Milestone
No milestone
Development

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