fix: change the ports scope in the network policy examples

[matheusmazzoni]

Description

Studying for CKS, I realized that the scope of ports was wrong in the official documentation. Since when giving an explanation in the network policy resource, I realized that the ports do not belong to to or from egress/ingress attributes, but rather, they are at the same level as them. So, I added this to the documentation

I noticed using kubectl:

$ kubectl version
Client Version: v1.32.1
Kustomize Version: v5.5.0
Server Version: v1.32.1

$ kubectl explain networkpolicy.spec.egress   
GROUP:      networking.k8s.io
KIND:       NetworkPolicy
VERSION:    v1

FIELD: egress <[]NetworkPolicyEgressRule>


DESCRIPTION:
    egress is a list of egress rules to be applied to the selected pods.
    Outgoing traffic is allowed if there are no NetworkPolicies selecting the
    pod (and cluster policy otherwise allows the traffic), OR if the traffic
    matches at least one egress rule across all of the NetworkPolicy objects
    whose podSelector matches the pod. If this field is empty then this
    NetworkPolicy limits all outgoing traffic (and serves solely to ensure that
    the pods it selects are isolated by default). This field is beta-level in
    1.8
    NetworkPolicyEgressRule describes a particular set of traffic that is
    allowed out of pods matched by a NetworkPolicySpec's podSelector. The
    traffic must match both ports and to. This type is beta-level in 1.8
    
FIELDS:
  ports <[]NetworkPolicyPort>
    ports is a list of destination ports for outgoing traffic. Each item in this
    list is combined using a logical OR. If this field is empty or missing, this
    rule matches all ports (traffic not restricted by port). If this field is
    present and contains at least one item, then this rule allows traffic only
    if the traffic matches at least one port in the list.

  to    <[]NetworkPolicyPeer>
    to is a list of destinations for outgoing traffic of pods selected for this
    rule. Items in this list are combined using a logical OR operation. If this
    field is empty or missing, this rule matches all destinations (traffic not
    restricted by destination). If this field is present and contains at least
    one item, this rule allows traffic only if the traffic matches at least one
    item in the to list.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: matheusmazzoni / name: Matheus Mazzoni (04869cf, 1f7a89d)

[k8s-ci-robot]

Welcome @matheusmazzoni!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	04869cf
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/682d2f3b42cbab00086539c1
😎 Deploy Preview	https://deploy-preview-50994--kubernetes-io-main-staging.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.

[windsonsea]

Hi @matheusmazzoni , it's recommended to only update the language/en version.
It's not necessary to inform so many localization approvers to review multi-language versions.

[matheusmazzoni]

Hi @matheusmazzoni , it's recommended to only update the language/en version. It's not necessary to inform so many localization approvers to review multi-language versions.

Sorry @windsonsea, I didn't know that. I'll update my PR changes to only update the language/en then.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign lmktfy 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:

• content/en/OWNERS

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

[windsonsea]

/remove-language bn es hi id ja ko pt zh