hierarchical-namespaces

hierarchical-namespaces copied to clipboard

Hi,

This is more cosmetic than anything else, but we have observed the 'kubectl hns tree' command is very slow to draw out the tree.

Is there any plans to improve this?

Thanks Mark

I haven't observed this, could it be that your apiserver is throttling replies? I'd generally expect one call to the apiserver per namespace, maybe two. How big is the tree you're trying to draw, and how long does it take? Is it faster if you just do a subset of the tree?

I suspect we could improve performance by using List calls instead to retrieve lots of information at the same time, though this wouldn't work if the caller didn't have read permissions to the entire cluster. Otherwise, we'd have to precompute data somewhere on the server and I'm not too excited about that either. I suppose HNC could support some additional endpoint (e.g. as an apiserver extension) but that seems like a lot of trouble as well.

In short, there aren't any plans to improve this and I'm not really sure where I'd start. That's assuming we don't find some clear bug, of course, which is certainly possible.

On Tue, Aug 30, 2022 at 5:51 PM Mark @.***> wrote:

Hi,

This is more cosmetic than anything else, but we have observed the 'kubectl hns tree' command is very slow to draw out the tree.

Is there any plans to improve this?

Thanks Mark

— Reply to this email directly, view it on GitHub https://github.com/kubernetes-sigs/hierarchical-namespaces/issues/223, or unsubscribe https://github.com/notifications/unsubscribe-auth/AE43PZGW77QGJEVVMYR7VALV3Z64HANCNFSM6AAAAAAQAZX3TA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

See also #226

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.