network-policy-api
network-policy-api copied to clipboard
Docs: a blog about v1alpha2 changes
Heya! I was going through the new API and saw there are a bunch of new changes, thought you could use a write up about them.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: frozenprocess Once this PR has been reviewed and has the lgtm label, please assign aojea for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
Deploy Preview for kubernetes-sigs-network-policy-api ready!
| Name | Link |
|---|---|
| Latest commit | a8445856eaf1d1fb1ea705a85c7947a920619c86 |
| Latest deploy log | https://app.netlify.com/projects/kubernetes-sigs-network-policy-api/deploys/68e439f4062aa500082d0794 |
| Deploy Preview | https://deploy-preview-328--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 project configuration.
Hi @frozenprocess. Thanks for your PR.
I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
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-sigs/prow repository.
/ok-to-test
Found a typo, and added an image.
thanks for your contribution @frozenprocess!
This blog is describing (not always accurately) the changes that are being done in the v1alpha2, which is done in more detail via a general effort of updating the docs here https://github.com/kubernetes-sigs/network-policy-api/pull/333.
What would be really valuable coming from the API users, is some more of your/your customers experience with the ANP/BANP and CNP, any feedback, real-world examples or maybe how your configurations have changed/will change with the new API.
Also your post mentions scalability improvements, if you have any examples for those it would be also really nice to see!
PR needs rebase.
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-sigs/prow repository.