Policy Assistant for ANP & BNP (repurposing Cyclonus)

[huntergregory]

User tooling for all three Policy APIs allowing you to:

• Experiment with AdminNetworkPolicy.
• Pre-validate how a policy will impact traffic on your cluster.
• Troubleshoot network issues:
  • "Do my policies drop traffic? Which one?"
• Summarize all policies.

Status Update (KubeCon EU 2024)

• demo
• slides
• code

Overview

New feature/design proposals always welcome!

User tooling for all Policy APIs.

Repurpose Cyclonus code into a Policy Assistant with these features:

1. Summarize policy interactions.
2. Analysis engine, simulating theoretical policy behavior.
3. Run conformance tests, which are quick to code by just specifying NetPols/(B)ANPs.

Builds off of #62, and replaces #69, breaking it into smaller issues.

Roadmap

NOTE: below list is out of date and will no longer be updated. Going to close this issue after the first CLI release #255.

Completed

• simulation: [Policy Assistant] Modify Data Structure for (B)ANP #152
• "explain" mode: [Policy Assistant] Summary Table for (B)ANP and NetPol #153

Next Up

Features

• "walkthrough" mode: [Policy Assistant] Predict Verdict and Flow of Decisions made by Policies #168
• [Policy Assistant] user experience for specifying pods/traffic #220
• "probe" mode: [Policy Assistant] Probe Mode #210
• improve CLI for "explain" mode: [Policy Assistant] explain command: support setting (B)ANPs via CLI arg #201
• conformance/fuzz testing: [Policy Assistant] Support (B)ANP in Cyclonus-based Conformance Tests #154
• [Policy Assistant] fix deny-all simulation for NPv1 #211
• [Policy Assistant] calculate all allowed connections in a cluster #221
• [Policy Assistant] warn about same-priority ANPs with overlapping rules #222

CI/CD, etc.

• [Policy Assistant] update binary names to policy-assistant instead of cyclonus #171
• [Policy Assistant] use internal vendoring instead of vendoring from Cyclonus #170
• [Policy Assistant] PR checks #202
• [Policy Assistant] Remove Cyclonus Code which isn't needed #151

[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

[huntergregory]

/remove-lifecycle stale

[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

[huntergregory]

/remove-lifecycle stale

[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

[huntergregory]

/remove-lifecycle stale

[huntergregory]

Going to close this issue after the first CLI release #255 . Future tracking can be done in other GH issues