Overview
OMC (OpenSearch Management Console) is a web-based management console for Opensearch clusters running on Kubernetes. It is built on top of the Opster Opensearch Operator and provides a user-friendly interface to help customers create, deploy, and manage Opensearch clusters on Kubernetes.
With OMC, users can easily manage Opensearch clusters — configuring them, monitoring their health, and performing updates. This document guides users through the installation process and provides detailed instructions for using all of OMC’s features. To get started, follow the instructions for deploying OMC on Kubernetes using Helm, which can be found on Artifact Hub at omc 1.9.6 · opster/opster-omc.
OMC simplifies management of Opensearch clusters running on Kubernetes, providing a streamlined interface for the performance of common tasks. Along with its basic features, OMC provides advanced features, such as rolling upgrades, backups and restores, version upgrades, and more. Whether deploying a new cluster or managing an existing one, OMC makes it easy to get the job done quickly and efficiently.
OMC can be deployed on any Kubernetes cluster using Helm package manager, making installation straightforward, and able to be up and running in minutes. The document provides step-by-step instructions for deploying OMC, so even if users are new to Kubernetes, they’ll be able to get started quickly. Once OMC is installed, users can access the management console through a web browser, making Opensearch clusters easy to manage from anywhere.
Visit Opster’s website for installation docs Install Opster Management Console – Opster.
How to Access OMC UI After Installation on Kubernetes
After installing OMC on the Kubernetes cluster, users can access the management console using a web browser. However, before accessing OMC UI, users need to forward a port from their local machine to the Kubernetes cluster. To do this, run the following command in the terminal:
kubectl port-forward service/operator-ui-svc 8080:5601
This command forwards traffic from port 8080 on any local machine to port 5601 on the Kubernetes cluster. This is the port which serves OMC UI.
After running this command, open the web browser and go to http://localhost:8080 to access the OMC UI.
Please note that the port-forwarding command must remain running in the terminal for as long as access to the OMC UI is required. Closing the terminal window or terminating the command means users will lose access to the OMC UI until running the command again.
In addition to using kubectl port-forward, users can also use the open-source software Kube-Forwarder to access the OMC UI from any local machine. Kube-Forwarder is a tool that facilitates access to services running in a Kubernetes cluster from any local machine, without the need for port-forwarding or VPNs.
Opster’s Auto-ops Integration
After installing the first OpenSearch cluster, it’s always a good idea to connect it to Opster’s Auto-ops for automated monitoring and maintenance. Opster’s Auto-ops is a powerful tool that can help identify and resolve issues in OpenSearch clusters before they become major problems.
To connect an OpenSearch cluster to Opster’s Auto-ops, sign up for a new Auto-ops account on the Opster website and follow the instructions using this link: New AutoOps Account – How to Connect Opster Metricbeat.
By connecting the OpenSearch cluster to Opster’s Auto-ops, users can ensure that clusters are running smoothly and efficiently, with minimal downtime and maximum performance.
