-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
NetworkPolicy Status - Features and parsing #2943
Comments
/sig network |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close |
@k8s-triage-robot: Closing this issue. In response to this:
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. |
/reopen |
@rikatz: Reopened this issue. In response to this:
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. |
Hi @ ! 1.24 Enhancements team here. Just checking in as we approach enhancements freeze ** TOMORROW ,18:00pm PT on Thursday Feb 3rd**. This enhancements is targeting
The status of this enhancement is track as |
Hi @gracenng KEP is ready to be merged, is under PRR review. Will probably get merged in the next few hours |
Hi @rikatz 1.24 Enhancements Team here, |
Hello @rikatz 👋 1.24 Release Comms team here. We have an opt-in process for the feature blog delivery. If you would like to publish a feature blog for this issue in this cycle, then please opt in on this tracking sheet. The deadline for submissions and the feature blog freeze is scheduled for 01:00 UTC Wednesday 23rd March 2022 / 18:00 PDT Tuesday 22nd March 2022. Other important dates for delivery and review are listed here: https://github.com/kubernetes/sig-release/tree/master/releases/release-1.24#timeline. For reference, here is the blog for 1.23. Please feel free to reach out any time to me or on the #release-comms channel with questions or comments. Thanks! |
Hi @rikatz , a friendly reminder that Code Freeze is coming in a few days. Please link your k/k enhancements here. |
Hi folks, sorry for the delay PR got merged: kubernetes/kubernetes#107963 Thanks |
Hi @rikatz, would you like to have this issue featured in the feature blog? If so, please open up a placeholder PR on kubernetes/website by March 30 which is our extended feature blog freeze deadline. Also, let me know if you do not have permission to edit the tracking sheet, I can do so on your behalf. Example of a feature blog PR: kubernetes/website#30538 |
/milestone clear |
Update on this: Me and @thockin discussed about the value on this, and also if NPP are willing to use webhooks or status. This was also discussed in sig-net meeting from 23/Jun/2022 and Netpol providers didn't have time to look into this, so we will give some spare time to check if using status in Netpol is something doable/desired/useful or if we will rollback and remove this |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. This bot triages issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /close not-planned |
@k8s-triage-robot: Closing this issue, marking it as "Not Planned". In response to this:
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. |
Plan is to undo this in v1.27 |
It's still alpha gated, though, right? |
@rikatz don't forget to nuke the code! |
/remove-label lead-opted-in |
Enhancement Description
k/enhancements
) update PR(s): KEP-2943: Add initial draft on Network Policy Status #2947k/k
) update PR(s): Implementation on Network Policy Status kubernetes#107963k/website
) update PR(s):Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.
The text was updated successfully, but these errors were encountered: