You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The viz dashboard is nearly unusable once the K8s cluster reaches a certain threshold of namespaces. In the case where K8s is being used to host workloads for customers, each in its own namespace, this problem may quickly arise.
How should the problem be solved?
Many of our namespaces have no linkerd connectivity, so being able to ignore namespaces via blocklist, glob patterns, or to manually specify an acceptlist of namespaces, all seem like valid solutions.
Any alternatives you've considered?
N/A
How would users interact with this feature?
This would be specified in the helm chart deployment, most likely.
Would you like to work on this feature?
Sure
The text was updated successfully, but these errors were encountered:
What problem are you trying to solve?
The viz dashboard is nearly unusable once the K8s cluster reaches a certain threshold of namespaces. In the case where K8s is being used to host workloads for customers, each in its own namespace, this problem may quickly arise.
How should the problem be solved?
Many of our namespaces have no linkerd connectivity, so being able to ignore namespaces via blocklist, glob patterns, or to manually specify an acceptlist of namespaces, all seem like valid solutions.
Any alternatives you've considered?
N/A
How would users interact with this feature?
This would be specified in the helm chart deployment, most likely.
Would you like to work on this feature?
Sure
The text was updated successfully, but these errors were encountered: