Komodor is a Kubernetes management platform that empowers everyone from Platform engineers to Developers to stop firefighting, simplify operations and proactively improve the health of their workloads and infrastructure.
Proactively detect & remediate issues in your clusters & workloads.
Easily operate & manage K8s clusters at scale.
Reduce costs without compromising on performance.
Empower developers with self-service K8s troubleshooting.
Simplify and accelerate K8s migration for everyone.
Fix things fast with AI-powered root cause analysis.
Explore our K8s guides, e-books and webinars.
Learn about K8s trends & best practices from our experts.
Listen to K8s adoption stories from seasoned industry veterans.
The missing UI for Helm – a simplified way of working with Helm.
Visualize Crossplane resources and speed up troubleshooting.
Validate, clean & secure your K8s YAMLs.
Navigate the community-driven K8s ecosystem map.
Kubernetes 101: A comprehensive guide
Expert tips for debugging Kubernetes
Tools and best practices
Kubernetes monitoring best practices
Understand Kubernetes & Container exit codes in simple terms
Exploring the building blocks of Kubernetes
Cost factors, challenges and solutions
Kubectl commands at your fingertips
Understanding K8s versions & getting the latest version
Rancher overview, tutorial and alternatives
Kubernetes management tools: Lens vs alternatives
Troubleshooting and fixing 5xx server errors
Solving common Git errors and issues
Who we are, and our promise for the future of K8s.
Have a question for us? Write us.
Come aboard the K8s ship – we’re hiring!
Hear’s what they’re saying about Komodor in the news.
Lens is an integrated development environment (IDE) that allows users to connect and manage multiple Kubernetes clusters on Mac, Windows and Linux platforms. It was originally developed by Kontena, a Finnish startup, and later acquired by Mirantis and open sourced under the MIT license.
Lens provides a graphical interface that:
You can download Lens for free from Github.
DevOps teams build applications using complex distributed architectures—they iterate locally and push out code to a sequence of Kubernetes clusters for testing, staging, and production using version control and CI/CD tools. Operators use the same tools to build and scale clusters. However, there is a lack of coordination in managing clusters.
Modern enterprises prioritize small, task-specific clusters over large ones. The result is that team members must handle many clusters (sometimes hundreds). The problem is that the CLIs that interact with clusters consume many files, making it harder to manage the complex, diverse range of methods and contexts.
Managing infrastructure from the command line is slow and error-prone, especially when scaling up applications and clusters. Likewise, configurations diverge, becoming more difficult to track. An IDE unifies the tools and information needed to work with different contexts and tasks.
Lens helps deal with these problems by:
Itiel Shwartz
Co-Founder & CTO
In my experience, here are tips that can help you better utilize Kubernetes Lens:
Use Lens to manage all your Kubernetes clusters from a single interface, reducing complexity and improving efficiency.
Leverage built-in Prometheus integration to monitor cluster health and performance metrics in real-time.
Explore and install Lens extensions to enhance functionality tailored to your specific needs.
Take advantage of Lens’s ability to manage multiple kubectl versions and kubeconfig files, simplifying cluster access.
kubectl
Utilize Lens Container Security to get CVE reports and enhance the security posture of your deployments.
Lens 6 is probably the most significant major release to date. New features include:
In addition, the new version introduces a different subscription model with the following tiers, effective from July, 2022, with a grace period for existing users until January, 2023:
There is no change to licensing for the community version, OpenLens, and also no changes to upstream projects used by Lens Desktop.
Download an installer suitable for your platform from the Lens website. Run the installer and open Lens. When you first open the app, you will be prompted to enter your Lens ID:
To perform an air-gapped installation when you don’t have an activation code, you can:
You are then prompted to choose Lens Personal or Lens Pro (a paid subscription with a 30-day trial). After you finish installation, the application automatically checks for and installs updates.
Lens searches common directories on your machine for kubeconfig files. On the welcome page, click Browse clusters in catalog to see clusters that were automatically discovered, such as local development clusters. You can click them and Lens will automatically connect to them.
To add a new cluster to the catalog, hover over the blue plus icon in the lower right corner of the screen. You can either copy paste from an existing kubeconfig file, or select an existing file to sync it with Lens.
The Helm package manager for Kubernetes is built into Lens and the popular bitnami chart repository is enabled by default. To add a new repository, from the operating system’s taskbar menu, click Lens and select Settings. In the Settings window, select Kubernetes and scroll down to the Helm Charts section.
Here you can add one of the listed repositories or select your own custom Helm repository.
Lens can run a small instance of Prometheus in the cluster and view metrics on the nodes, depending on the RBAC permissions in the account. If you’re already running Prometheus, you can export metrics from that instance to Lens.
To configure metrics, right-click the Cluster icon in the left-hand navigation and select Settings > Metrics. Select a metric to connect to an existing metric system (such as an existing Prometheus instance).
After you select the metric, if you choose the option of creating a new Prometheus instance, it will take a minute or two to start. Lens connects to Prometheus, and cluster metrics automatically appear in the cluster dashboard.
Lens lets you view all objects and abstractions in your Kubernetes cluster. To see the types of resources available, from the left hand navigation, select Workloads. The Overview screen appears, which shows a summary of the types and number of resources running in your cluster.
You can edit, save and reapply YAML in the built-in editor, by drilling down anywhere and right-clicking on the submenu associated with an item. Developers with private clusters can quickly iterate and see results in real-time. Shared clusters fully integrate role-based access control (RBAC) to ensure that only users with the appropriate credentials can access and edit objects in the cluster.
Lens also allows you to click any container to run a terminal window inside the container, or fetch container and pod logs. If you’re using infrastructure as code (IaC), Lens lets you open any number of terminals and quickly browse your local repositories to find the files you need. For example, you can push changes to Git, run Docker commands, or open files in your IDE or editor for modification and version control.
Kubernetes Lens is a great tool but has its disadvantages. Here are three popular solutions DevOps teams are considering as alternatives to Lens.
Product info: https://komodor.com/
Signup: https://app.komodor.com/#mode=signUp
Komodor is an end-to-end Kubernetes operations solution for Dev and Ops teams that is designed to bring back control over your Kubernetes environment.
Komodor provides automated playbooks for every K8s resource, and static-prevention monitors that enrich live & historical data with contextual insights to help enforce best practices and stop incidents in their tracks. By baking K8s expertise directly into the product, Komodor is accelerating response times, reducing MTTR and empowering dev teams to resolve issues efficiently and independently.
Key features:
GitHub: https://github.com/rancher/dashboard
License: Apache License 2.0
Rancher is a popular Kubernetes multi-cluster management solution. The Rancher Dashboard is a stateless client for the Rancher API, built with Vue.js and NuxtJS. It is built and packaged as a folder of static HTML/CSS/JS files that are bundled with all Rancher releases. When you use rancher, the Rancher Dashboard index.html file is displayed as a fallback for any request that doesn’t match a specific API URL.
Rancher Dashboard shows all Kubernetes types, namespaces, and actions that the authenticated user has access to. The default views are raw YAML from the Kubernetes API, with a detail page and table view for list pages (kubectl get commands). You can customize columns to create your own view of configurations and resource listings.
GitHub: https://github.com/skooner-k8s/skooner
Skooner provides a Kuberntes dashboard including configuration and workload views, and the ability to edit YAML directly in the UI. Additional features include:
Together with our content partners, we have authored in-depth guides on several other topics that can also be useful as you explore the world of Kubernetes.
Authored by Komodor
Authored by Granulate
Authored by Tigera
Share:
and start using Komodor in seconds!
