network-policy-api icon indicating copy to clipboard operation
network-policy-api copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

Gather use cases for service accounts as selectors

Open tssurya opened this issue 1 year ago • 6 comments

This came from discussions at KubeCon, I want to make sure they are captured here correctly. Closes: #173

tssurya avatar Nov 19 '24 10:11 tssurya

Deploy Preview for kubernetes-sigs-network-policy-api ready!

Name Link
Latest commit c53903f22fc5585d2208116ca05e8ca142dc070e
Latest deploy log https://app.netlify.com/sites/kubernetes-sigs-network-policy-api/deploys/674575a1f736e20008a0987a
Deploy Preview https://deploy-preview-274--kubernetes-sigs-network-policy-api.netlify.app
Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

netlify[bot] avatar Nov 19 '24 10:11 netlify[bot]

Thanks for writing this up @tssurya!

/cc @robscott @LiorLieberman

robscott avatar Nov 25 '24 18:11 robscott

I will take a look at this ASAP, too (rough with US holiday this week).

thockin avatar Nov 25 '24 20:11 thockin

lots of comments here! :) will look through them and try to cover/reflect the discussions or at least write it down in the next update I push

tssurya avatar Dec 03 '24 16:12 tssurya

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle stale

k8s-triage-robot avatar May 21 '25 20:05 k8s-triage-robot

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

This bot triages 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 PR is closed

You can:

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

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

/lifecycle rotten

k8s-triage-robot avatar Jun 24 '25 20:06 k8s-triage-robot

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

This bot triages 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

k8s-triage-robot avatar Aug 03 '25 03:08 k8s-triage-robot

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/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-sigs/prow repository.

k8s-ci-robot avatar Aug 03 '25 03:08 k8s-ci-robot

/reopen

tssurya avatar Aug 03 '25 08:08 tssurya

@tssurya: Reopened this PR.

In response to this:

/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-sigs/prow repository.

k8s-ci-robot avatar Aug 03 '25 08:08 k8s-ci-robot

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: tssurya Once this PR has been reviewed and has the lgtm label, please assign aojea for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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 avatar Aug 03 '25 08:08 k8s-ci-robot

/remove-lifecycle stale

tssurya avatar Aug 03 '25 08:08 tssurya

Somehow I missed this whole thread until it is now "stale"

oops yea I think there is work on multiple fronts in GAMMA communities as well: https://github.com/kubernetes-sigs/gateway-api/issues/3566 and then another separate google doc that was also done.. I wasn't/ain't sure of the latest status though on the L7 side

I'll reopen this issue and see if I can capture the latest based on all comments - at least that's good to have the history captured in this repo at least for the network policy APIs.

tssurya avatar Aug 03 '25 08:08 tssurya

/lifecycle frozen

adding this label so that bot doesn't close this issue. I'll spend some time on this during the 1.35 release to make it more recent based on the all conversations that have happened.

tssurya avatar Aug 03 '25 08:08 tssurya

@tssurya: The lifecycle/frozen label cannot be applied to Pull Requests.

In response to this:

/lifecycle frozen

adding this label so that bot doesn't close this issue. I'll spend some time on this during the 1.35 release to make it more recent based on the all conversations that have happened.

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-sigs/prow repository.

k8s-ci-robot avatar Aug 03 '25 08:08 k8s-ci-robot

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

This bot triages 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/close

k8s-triage-robot avatar Sep 02 '25 08:09 k8s-triage-robot

@k8s-triage-robot: Closed this PR.

In response to this:

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

This bot triages 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 PR is closed

You can:

  • Reopen this PR with /reopen
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Offer to help out with Issue Triage

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

/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-sigs/prow repository.

k8s-ci-robot avatar Sep 02 '25 08:09 k8s-ci-robot