Warnings from Kubernetes v1.34 API discovery: Endpoints and ComponentStatus deprecation warnings during detect-all-in-cluster

[DeepAgr]

What happened?

Summary

When running Pluto against a Kubernetes v1.34 cluster, the scan completes successfully but emits deprecation warnings during API discovery:

Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Warning: v1 ComponentStatus is deprecated in v1.19+
No deprecated API versions found

The warnings appear even though there are no deprecated resources in the cluster.

Environment
Pluto version: 5.24.0
Kubernetes version: v1.34
Target version: v1.35.0

Command
pluto detect-all-in-cluster -t k8s=v1.35.0

Output
Warning: v1 Endpoints is deprecated in v1.33+; use discovery.k8s.io/v1 EndpointSlice
Warning: v1 ComponentStatus is deprecated in v1.19+
No deprecated API versions found

What did you expect to happen?

The scan should complete without generating Kubernetes API deprecation warnings if possible.

If these warnings originate from API discovery performed by Pluto or its Kubernetes client dependencies, it would be helpful if Pluto could avoid querying deprecated resources (such as ComponentStatus and legacy Endpoints) or otherwise suppress these expected discovery warnings.

How can we reproduce this?

Environment
Pluto version: 5.24.0
Kubernetes version: v1.34
Target version: v1.35.0

Command
pluto detect-all-in-cluster -t k8s=v1.35.0

Version

Version:5.24.0 Commit:dd5ec8cccce5e42dfe8054b8250baa35546056a0

Search

• I did search for other open and closed issues before opening this.

Code of Conduct

• I agree to follow this project's Code of Conduct

Additional context

The scan itself completes successfully and correctly reports that there are no deprecated API versions in the cluster. The issue is only the deprecation warnings printed during discovery.

Please let me know if you would like any additional logs or if I can help test a fix.

[sudermanjr]

Thanks for the detailed report!

Does #604 work?