kubespy icon indicating copy to clipboard operation
kubespy copied to clipboard

Support tracing nodes / or any resource type

Open mweibel opened this issue 1 year ago • 2 comments

What happened?

Filling this as a bug because README mentions as feature that it supports any kind of resource.

I wanted to trace a node but unfortunately it doesn't work:

» kubespy trace nodes $name
Unknown resource type 'nodes'. The following resources are available:
  - service (aliases: {svc})
  - deployment (aliases: {deploy})

Example

kubespy trace nodes $name

Output of pulumi about

doesn't apply here

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

mweibel avatar Jun 26 '24 06:06 mweibel

Using changes:

» kubespy changes v1 $name
the server could not find the requested resource

In this case I believe the issue is Cluster vs Namespace scope because watch.Forever always specifies a namespace: https://github.com/pulumi/kubespy/blob/318db5007c800a5624187ef7d1b785f4dfaae554/watch/watch.go#L104

mweibel avatar Jun 26 '24 06:06 mweibel

Thanks for creating this @mweibel! We should probably update the README to specify the set of resources currently supported (services, pods, deployments, replica sets). We'll update the README and keep this as a feature request for additional types.

blampe avatar Jul 01 '24 17:07 blampe