The Monokle Team at Kubeshop is proud to announce version 1.5.0 of Monokle, our open-source desktop tool to help you with all-thing-related to Kubernetes manifests.
The Monokle Team at Kubeshop is proud to announce version 1.5.0 of Monokle, our open-source desktop tool to help you with all-thing-related to Kubernetes manifests.
This is a truly massive release with a slew of new features, both big and small, aimed at both those new to Kubernetes and those that are deep into it. Let’s dive in!
Monokle now provides templates to help you get started with creating resources. Templates are available from a Template Explorer on the left:
Selecting a template will prompt you for corresponding input and result in one or more created resources interpolated with the provided values - for example the “Basic Service” template:
After providing required information Monokle will generate the corresponding resources:
Monokle comes with a number of default templates for creating basic Kubernetes resources (bundled in our monokle-default-templates-plugin) - but you can easily create your own templates and use them in Monokle; check out the templates and plugins documentation to dig in!
Monokle introduces the concept of projects - with a dedicated project selector at the top of the UI to make it easy to switch between projects, create new ones, etc.
The settings now correspondingly have both default project settings (that will be applied to newly created projects) and the settings of the current project:
Monokle now has integrated support for Istio and Cert-Manager CRDs - resulting in:
Cert-Manager example:
Istio example:
The upcoming 1.6.0 release will include support for more resource types (Flux, Argo, etc) - let us know which ones you think we should support!
Editing Kubernetes Secret manifests has never been easier - the Secret form editor now has integrated support for all Secret types with automatic base64 encoding/decoding in applicable form fields.
Apart from the Secret editor mentioned above, the integrated Form editors now have support for NetworkPolicies and have been extended with settings to control their behavior in regard to default values provided by the underlying JSON Schema.
Previously, the Form Editor would always insert default values for both complex and primitive values - which could be annoying as this might change the underlying YAML without any changes made in the UI. On the other hand, inserting default values can be helpful as it makes a manifest more explicit and helps users understand possible settings/values. Using these settings you can decide which behaviour that best fits your needs.
Monokle will now “learn” any CRDs it encounters during parsing of resources to provide schema validation and Form editors for corresponding resource kinds (these will be “forgotten” when Monokle is restarted). For example after connecting to a cluster containing ArgoCD you will see syntax errors and documentation hints in the editor and have access to corresponding Form editors for ArgoCD objects:.
It is now possible to select multiple resources - which opens a corresponding action-bar at the top of the navigator.
The underlying logic for validating links has been improved to be aware of link qualifiers like namespace and resourceKind. For example the below subject link is marked as invalid because the target ServiceAccount is not in the correct namespace.
A number of actions have been added to the file and folder popup menus - including actions to
Monokle now touts a nice Getting Started page prompting you to open an existing project or create a new one. As before, there is a global setting to bypass this page and immediately load the project last worked on.
Selecting your current target cluster is now done from the top panel - the corresponding button on the left toolbar has been removed.
Configure your kubeconfig in the Project Settings panel:
As always you can download the release from GitHub and get in touch to complain or praise Monokle on our Discord Server - looking forward to hearing from you!