Andrey Pokhilko

The confusion is probably around the way you reference the consumed message. Pay attention to `consumed.` prefix of values referenced. In your example, you have the just `someId` referenced. Looks...

My bad. Can you look at this PR? https://github.com/up9inc/mockintosh/pull/167 There is an example of expression there, looks exactly applying to your case

This looks very unusual, since it's a basic shell script inside. However, there is a workaround for you: you can just download the appropriate [release package](https://github.com/komodorio/helm-dashboard/releases) for your platform, unpack...

No more feedback received...

DaemonSet and StatefulSet are in theory similar to Deployment object. It would be good to display more relevant status information for those, if possible. For now, we have to do...

Deploying it into k8s would raise a security concern, because it would become accessible from multiple locations. This would raise the authentication questions etc. For now I thought all these...

Yes, it is still open. It assumes a step in `release.yaml` that will check that plugin.yaml version matches tag name.

No, we can't generate `plugin.yaml` by action. The validation step is a safety valve that just checks that content of a certain field inside `plugin.yaml` matches `github.ref_name`

It's mostly about this file: https://github.com/komodorio/helm-dashboard/blob/main/pkg/dashboard/subproc/data.go Also take into account a discussion that took place in #77

Can you share more background on this? Why standard Helm way of installing the plugin is not sufficient for you?