Port ranges in network policies are not rendered

[rthrippleton]

Describe the bug When a network policy contains a TCP port range, that range is shown as an individual port rather than a range in the describe view and the list view.

To Reproduce Create a network policy with a port range e.g.

  - ports:                                                                                                                                                                                                                                                                                                                     
    - endPort: 5200                                                                                                                                                                                                                                                                                                            
      port: 5000                                                                                                                                                                                                                                                                                                               
      protocol: TCP

then locate it in the list view and notice that it only describes it as TCP:5000, and similarly in the describe ('d') view.

Expected behavior Expect to see a description of the port range.

Versions (please complete the following information):

• OS: Linux amd64
• K9s: 0.32.3
• K8s: k3s v1.26.14+k3s1

[derailed]

@rthrippleton Not an excuse, but I think on part with kubectl (since we use the same api) What does k describe netpol xxx report?

[rthrippleton]

Oh, you're absolutely right!

From my YAML above, the equivalent kubectl describe is

    ----------
    To Port: 5000/TCP
    From: <any> (traffic not restricted by source)

Is this going to be the same reason behind the list view showing TCP:5000 for the ING-PORTS column?

Out of interest, does k9s used whatever kubectl is on the path, or does it have its own embedded? I think my local install has a fairly old install of kubectl, and maybe this issue got fixed in a later one?