Monokle version 1.3.0 — our open source tool for managing Kubernetes manifests — with some truly exciting new functionality and requested features to make developers lives easier like...
We’re super-excited to release version 1.3.0 of Monokle — our open source tool for managing Kubernetes manifests — with some truly exciting new functionality and requested features to make developers lives easier like:
The (truly awesome!) Cluster-Compare functionality provides you with an interactive UI to compare a set of local resources (either static or generated by Helm/Kustomize) to those in your cluster, allowing you to easily
No more fumbling with manual/command-line approaches to understanding the impact your manifests will have on your cluster configuration when deployed — Monokle will give you that nice overview you have craved since your first helm-diff!
To give you a better idea of the workflow, here comes a short video showing you how it works:
As before Monokle automatically validates all loaded resources against their corresponding kubernetes schema and also checks the integrity of links/references between all resources.
The total number of errors is now shown at the top of the resource navigator — with a corresponding popup that shows a list of invalid resources.
Clicking a resource will automatically select and open it for editing — so you can easily find the cause of the error and hopefully fix it directly.
We’ve added a notification center that allows you to see all past notifications:
If your specified kubeconfig file contains multiple contexts Monokle will detect those and allow you to select which one to use for cluster-related operations:
We now provide a bunch of packages for various Linux distros:
Monokle now does not flag incorrect optional references as errors in resources:
In this screenshot you can see that the configMapKeyRef has optional set to true - resulting in no error for the invalid name reference (vs the one below which has optional set to false).
This behavior can be disabled in the Settings pane
resulting in errors shown for optional references also:
Monokle previously didn’t show any resources which it didn’t recognize, now it shows these under a dedicated “Unknown” section at the bottom of the Navigator.
(The upcoming plugin-framework will allow you to provide custom validation/linking/editing services for resource kinds not handled natively by Monokle)
As always we’re super-excited about the release:
Writing “good” policies is a complex, time-consuming task. Learn to build and troubleshoot policies interactively – with immediate feedback with the power of Monokle Cloud.
Have you been struggling to adopt Kubernetes Pod Security Standards? Monokle is here to help!
Join the Monokle Community in one of these channels: