set future course for network policy engine + conformance (formerly: Cyclonus)

[mattfenwick]

Follow up on #34 -- what is the future of this network policy tool?

I suggest considering:

• rename to something appropriate for kubernetes-sigs (positive side effect: disambiguates from my personal project)
• define goals
  • engine
    • features
      • ANP
      • BANP
    • applications
      • understand use cases -- CI, end user, [Feature Request] - Ability to Simulate a Network Policy #46
  • conformance suite
    • ANP
    • BANP
  • builds, distros, devex
    • binaries
    • images
    • kubectl plugin
    • yaml for k8s deploys

Note: this is just off the top of my head, I'm sure there are more things to consider.

[mattfenwick]

@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!

[astoycos]

/assign

[olivercodes]

@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?

[astoycos]

/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

[olivercodes]

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

[olivercodes]

@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 Publish Cyclonus images to GHCR #68
• Any ideas for name @mattfenwick ?

[k8s-triage-robot]

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-triage-robot]

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

[k8s-triage-robot]

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

[k8s-ci-robot]

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

In response to this:

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

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.