Skip to content

[Feature]: note networkPolicy objects that use port numbers rather than names. #565

@jcpunk

Description

@jcpunk

Is your feature request related to a problem? Please describe.
When matching networkPolicy to a service, it is easy to use a port number, but a named port is more scalable.

Describe the solution you'd like
Like with liveness and readiness probes, note use of explicit ports rather than names.

Describe alternatives you've considered
Checking by hand

Additional context
https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.35/#networkpolicyport-v1-networking-k8s-io

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions