Closed tssurya closed 3 months ago
Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all
Name | Link |
---|---|
Latest commit | 4d5dd786cebd610814270e5c3768505b244586c6 |
Latest deploy log | https://app.netlify.com/sites/kubernetes-sigs-network-policy-api/deploys/6601cdc9ffb5d30008fc09f3 |
Deploy Preview | https://deploy-preview-196--kubernetes-sigs-network-policy-api.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
/hold need to remove conformance plumbing and need to bring it up in upstream meeting before merging this.
/hold cancel
/hold
Until the work as part of the Tenancy NPEP ends up as an actual API change PR, I'll let @npinaeva remove this hold
PR needs rebase.
/lgtm /approve
not doing "/hold cancel" because I'm not totally sure why it's held, but I think it's ok to merge
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: danwinship, tssurya
The full list of commands accepted by this bot can be found here.
The pull request process is described here
/hold cancel
Let's get rid of this unwanted API
/lgtm thanks @tssurya
We have been extensively re-designing our tenancy use cases and its clear we won't be using same and notSame labels: https://github.com/kubernetes-sigs/network-policy-api/pull/178#issuecomment-1930447439 Let's remove this from our API before it hits Beta. See FUP issues that need to be fixed once this merges in : https://github.com/kubernetes-sigs/network-policy-api/issues/197
We had a certain asymmetry around how
namespaces
insubject
andnamespaces
inpeers
are used. This was because thenamespaces
in subject was a simplenamespaceSelector
while the one in the peer was a struct type withnamespaceSelector
,sameLabels
andnotSameLabels
. However since we are removingsameLabels
andnotSameLabels
there is no need fornamespaces
in peer to be a struct, we can just make thisnamespaceSelector
thus bringing it closer to how it looks in the subject.and
if that makes it confusing ^ we can think of alternatives