Update the user stories to ClusterNetworkPolicy

[bowei]

Fixes the user-story-*.yamls

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: bowei
Once this PR has been reviewed and has the lgtm label, please assign danwinship for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[netlify]

✅ Deploy Preview for kubernetes-sigs-network-policy-api ready!

Name	Link
🔨 Latest commit	62b2836
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-network-policy-api/deploys/68e054e1748d520008841982
😎 Deploy Preview	https://deploy-preview-321--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.

[npinaeva]

nice! could you also update https://github.com/kubernetes-sigs/network-policy-api/blob/main/site-src/reference/examples.md as it reuses the same examples?

[danwinship]

Is there value in keeping the existing ANP user stories as-is for historical reasons?

[bowei]

Depends on the usage -- if it's for reference, Git history is sufficient. If you want to be able to reference it online (e.g. via live hyperlink), then we need to make a copy and preserve it.

I am of the opinion that the value of keeping it around is most valuable right now, but the value will keep going down from here on out -- therefore, it doesn't seem like it's that important...

[npinaeva]

Is there value in keeping the existing ANP user stories as-is for historical reasons?

The user stories are kinda left as is, mostly the implementation yamls are being updated

[bowei]

I just updated incorporating the comments, please take a look.