Ziv Nevo

Pods behind Services with the annotation `prometheus.io/scrape: "true"` should allow in-cluster ingress into port 9090. If, in addition, the Service has the annotation `prometheus.io/port`, use the specified port instead.

If two workloads in the same namespace have exactly the same labels and have exactly the same required connections, two identical netpols (except for name) might be generated. While this...

Allow the user to set the level of netpol permissiveness

1

Some options: * Only allow connections identified by the algorithm * If a service exists, but no incoming connections detected, open the service to the whole namespace * If a...

Suggestions from @vikin91 : - [x] use assertion package to reduce the amount of code and unify the failure messages (e.g., https://github.com/stretchr/testify) - [x] convert the isolated test cases into...

- [ ] Specify input format for the list of required connections - [ ] Provide an API call to synthesize from this list - [ ] Provide a CLI...

A flag to output netpols as separate YAML documents/files

1

rather than a single NetworkPolicyList resource

Is the Peer CRD the right place for this?

Probably set in the Export CRD. How do we publish these attributes to all remote peers that import the service?