Ashish Tiwari

@nishantwrp All channels in hub are unbufferred. This might become a bottleneck so make these channels bufferred unless some synchronization is required so that clients don't block on send.

@asubedy The below rows still display results for a single version. Let's have k8s version as an extra column here 

> @Revolyssup please triage the issue. Are you going to complete this or should it be reassigned? Putting this under a clickup task to track there and will get back...

@CyrineG In this PR, meshery-operator's Chart.yaml has adapter's charts in dependencies. This should not be the case. Meshery server or any of Meshery adapters like `meshery-istio` , `meshery-linkerd` should not...

> @Revolyssup done! Have you tried installing these charts in different flows? I will checkout your branch and perform the below tests. Meanwhile if you get time before me, make...

@CyrineG Try putting meshery-meshsync and meshery-broker charts only in meshery-operator chart. And in Meshery chart, make just meshery-operator as a local dependency.

@CyrineG Can you solve the merge conflicts?

@CyrineG So by default meshery chart installs operator. The only caviat is, when operator is installed with `meshery` chart then it comes under the release name `meshery`. But when users...

> @Revolyssup Looking at [this](https://codeutility.org/kubernetes-where-to-override-release-name-in-helm-stack-overflow/) it doesn't seem possible for a subchart to override the release name that was defined by `Helm install`. The same happens when I deploy meshery...

@jbyers19 So how is this PR coming up? Are you feeling alright to continue this?