monokle
monokle copied to clipboard
kubeshop
Feedback about Monokle? we would love to hear it!
Hi everybody! first of all, thanks for using Monokle 🧐
We value your feedback as we update our roadmap based on our user feedback. Please let us know what do you think in the comments below:
- How are you using Monokle (i.e what problems it helps you the most)?
- What would you like to see?
- What bothers you?
Wanna chat with us? Find us on Discord
I've already discussed this with one of the developers, but in my case (m1 mac os monterey 13.1 and macbook pro), when I open a chart (in this case NATS helm) and go to "Helm Charts" I see that the values file is called alues.yaml. Exactly the same behaviour on both laptops.
fyi:
helm repo add nats https://nats-io.github.io/k8s/helm/charts/
helm pull nats/nats
Hi @lethargosapatheia , I've created an issue about that here https://github.com/kubeshop/monokle/issues/1647 and we finally have a way to reproduce the error. This will get fixed as soon as possible and will be available in the 1.7 release or in one of the nightly builds.
I'd love to see Kyverno support added for policy management. Personally, I think writing custom policies in OPA is ridiculously confusing, so I am not really a fan of it.
If you're looking to adopt a more general purpose policy solution, I would explore JSPolicy. It seems that Loft has abandoned the project, but I would rather use JavaScript to define policies rather than OPA's "special" language.
thank you @pcgeek86 - we're looking into supporting alternative policy engines - agree that rego/OPA isn't the most natural of languages... i've created https://github.com/kubeshop/monokle/issues/2639 - please add more details/ideas/suggestions there if you have any!
Your Discord invites and links seem to be invalid.
Hey @deiga, the link to our Discord channel from the description was updated. You should be able to get an invite to join it.
I'd love to see Kyverno support added for policy management. Personally, I think writing custom policies in OPA is ridiculously confusing, so I am not really a fan of it.
If you're looking to adopt a more general purpose policy solution, I would explore JSPolicy. It seems that Loft has abandoned the project, but I would rather use JavaScript to define policies rather than OPA's "special" language.
Hello @pcgeek86, we've been working on custom validation with TypeScript and I believe you might love it. We value user feedback a lot so I was wondering if you're interested in joining our Discord. That way I can invite you for a small one-on-one session where you can get a sneak preview of the feature and we can find out whether it solves your frustrations with OPA.
@WitoDelnat I'm actually in the Discord server already. My username is pcgeek86#5950
When I connect my cluster to monokle it basically brings up the numbers of all the workloads and services that I have in my cluster and then freezes and I cannot use the system.
I was hoping to be able to replace lens with Monokle because of recent issues from the lensapp team, but at this point in time, the speed of connecting to my cluster is way to slow and I would not be able to use it.
thanks for your feedback @absmith82 - improving performance is top priority for our next release - hopefully that will make Monokle a viable alternative to Lens going forward - we'll let you know once it's released!
IMO, on startup, the app should block until the telemetry question has been answered.
Before I can even answer the question, the app apparently spawns kubectl and Python, querying (all of?) my control planes. And apparently due to the performance issues (v2.0.4), I amass ~700 processes each of kubectl and Python --before the system halts. You should at least wait before the telemetry question has been answered.
Thank you, @matthewhembree, for the feedback. We will address this very soon.
@matthewhembree, Regarding the ~700 processes, how many contexts do you have?
@matthewhembree, Regarding the
~700 processes, how many contexts do you have?
Hi @mortada-codes I have 20 contexts. Some have a decently large number of namespaces. The largest has ~130 namespaces. Second is ~90.
If this behavior is unexpected for that number of contexts:namespaces, I can create a separate issue.
Hey @matthewhembree, you can now try the nightly build https://github.com/kubeshop/monokle/releases/tag/v2.0.6-nightly-2023-03-21.0
Sad first experience on Windows:
- prerequirements not handled by installer and not described anywhere (maybe should be going by Lens way without painful PATH configuration?)
- errors warnings, tooltips have not enought detials to fix by self (also impossible to find somthing in repo or docs about it)
-
(there is no tooltip or something!)
-
(incorrect tooltip for inactive button, expect reason)
-
-
- telemetry enabled by default
Anyway app looks great, but I think need an extra year for this tool to be more pleasure for new users.
thanks @npdev453 for reporting - that's definitely a sad experience.. we'll dig in 👍
In v2.4 there is no more button to deploy my helm chart, only to preview dry-run. It was a convinient way to deploy charts with specific set of values and parameters, now gone :( Please, bring it back. But nevertheless Monocle is a great app, thank you very much for your work!
hi @Anemun , I just checked and it looks like we still have the Install button in the header of the Code Editor when you have a Values file selected, but it is missing for "Dry Run Configurations".
This is a bug related to selections and we will fix this as soon as possbile.
You can still deploy a Values file by selecting it in the File Explorer instead of the Dry-runs panel.
But for the configurations we'll have to publish the fix. Thanks for reporting it!
What do you think of the rework we did for the UI of the dry runs? Do you like it better than 2.3.x? Any feedback?
@devcatalin thank you! I mostly like the rework, it became more clearer and simpler to run. But in charts with many subcharts the list of dry-runs becoming very long, more scrolling required. Though now there is no need to create every dry-run configuration manually, that's a plus.
If we are talking about dry-run configurations, I have a suggestion. In current build, when you create dry-run configuration, you choose either it will be Template or Install. Maybe, make it as a button like "Deploy"? For example, I have a dry-run configuration with specific values and parameters and I want to first run Template, then Dry-run, then Install, without changing configuration itself.
For me was a really strange that there no autocompletion for kustomize at all. but at https://github.com/vscode-kubernetes-tools/vscode-kubernetes-tools/issues/824 it was advertized as a best support for kustomize. Take a look on https://github.com/Allaman/kustomize.nvim - this is an example of such support
Hi @simonoff - thanks for your feedback! You should be getting auto-complete for kustomize overlays - see screenshot below - in what way was this not working?
Also - what really sets Monokle apart when it comes to Kustomize is the possibility to interactively dry-run kustomize overlays to see / validate / compare their output. Afaik no other tool allows you to do that.. Happy to hear any other comments/requests from you - please share!
As for me biggest pitfall is that i'm unable to autocomplete the files. For example, i have a folder with kustomize.yaml and a list of files. In neovim I just use same autocomplete to autocomplete the files inside such folder. In VSCode and your editor - need to write them manually.
thanks @simonoff ! just to be 100% sure that we understand your issue - could you share a screenshot or short video of how it works in neovim and not in Monokle/VS-Code? Really appreciate your help!