set future course for network policy engine + conformance (formerly: Cyclonus) about network-policy-api HOT 10 CLOSED

@astoycos feel free to close if this isn't useful, I see problems like: build scripts in this repo point to my personal repos, and want to figure out how I can help the community to tackle them!

from network-policy-api.

/assign

from network-policy-api.

@mattfenwick @astoycos happy to file some issues against this.

For Build/Distribution related items, would we want to publish to registry.k8s.io? Or just under releases on our repo?

from network-policy-api.

/assign @olivercodes

thanks that would be great!

For Build/Distribution related items, would we want to publish to registry.k8s.io? Or just under releases on our repo?

Let's talk about this in today's meeting

from network-policy-api.

Confirmed in 12/5 meeting, we'll use GHCR. No binaries for now, may change in future if need/convenience for someone is there.

from network-policy-api.

@mattfenwick @astoycos

Engine one created here - #69

Can probably track "add conformance suite" with the original conformance tests issue? - #35

Kubectl Plugin

• I don't think we've really discussed the lifecycle/usage of the kubectl plugin yet (and admittedly I'm not as familiar with it yet, other than what Matt showed me). Probably a good topic for next meeting.

Rename the tool

• Probably want to decide on that before someone tackles #68
• Any ideas for name @mattfenwick ?

from network-policy-api.

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

from network-policy-api.

The Kubernetes project currently lacks enough active 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 rotten
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

from network-policy-api.

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:

• 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:

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

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

/close not-planned

from network-policy-api.

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

from network-policy-api.