External labels on kubernetes aren't useful

[hookenz]

Before you start please confirm the following.

• Yes, I've searched similar issues on GitHub.
• Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description

Can you consider removing the label "external" on Kubernetes resources?

It's just a lot of table clutter and many resources end up marked external anyway.

Also Portainer has a hard time getting it right. But also anything not deployed directly by Portainer will be external.
I don't think many would care if it's external or not. It isn't that beneficial from a Kubernetes point of view.

Just my opinion.

Sorry I created this as a bug because it appears that discussion points don't seem to be acknowledged or read. Correct me if I'm wrong there.

Expected Behavior

It should work. But it doesn't always seem to be right.

Actual Behavior

Remove them for Kubernetes

Steps to Reproduce

See above

Portainer logs or screenshots

No response

Portainer version

2.34.0

Portainer Edition

Business Edition (BE/EE) with 5NF / 3NF license

Platform and Version

Kubernetes

OS and Architecture

Linux

Browser

firefox

What command did you use to deploy Portainer?

standard

Additional Information

No response

[Nick-Portainer]

Hi @hookenz I have moved this over to an idea. We actively monitor these and if they build traction it's raised internally