opensearch
Use when installing or configuring the OpenSearch extension for KubeSphere, which provides distributed search and analytics engine for storing logs, events, auditing, and notification history
Profile →npx skills add kubesphere/kubesphere --skill opensearch --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# OpenSearch Extension ## Overview OpenSearch is a distributed search and analytics engine built into the KubeSphere WizTelemetry Observability Platform. It is used to store, search, and analyze observability data including logs, auditing events, K8s events, and notification history. ## When to Use - Installing OpenSearch cluster for KubeSphere observability extensions - Configuring OpenSearch storage for logging, events, auditing, and notifications - Managing OpenSearch Dashboard and Curator components ## Components | Component | Description | Default | |-----------|-------------|---------| | opensearch-master | Master node for cluster coordination | 1 replica | | opensearch-data | Data nodes for storing indices | 3 replicas | | opensearch-dashboards | Web UI for visualizing data | disabled | | opensearch-curator | Scheduled task to clean old indices | enabled | ## Prerequisites ### Check Installation Status ```bash # Check if OpenSearch is installed kubectl get installplan opensearch -o jsonpath='{.spec.enabled}' # Get installed version kubectl get extension opensearch -o jsonpath='{.status.installedVersion}' # Get target clusters kubectl get installplan opensearch -o jsonpath='{
- Overview
- When to Use
- Components
- Prerequisites
- Check Installation Status
- Get Available Clusters
- Confirm Target Clusters (MUST DO)
- Get Latest Version
- Installation
- Minimal Installation
- With OpenSearch Dashboard
- Disable Curator
- Configuration
- Parameters
Check if OpenSearch is installed
kubectl get installplan opensearch -o jsonpath='{.spec.enabled}'
Get installed version
kubectl get extension opensearch -o jsonpath='{.status.installedVersion}'
Get target clusters
kubectl get installplan opensearch -o jsonpath='{.spec.clusterScheduling.placement.clusters}'
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
kubectl get extensionversions -l kubesphere.io/extension-ref=opensearch -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
kubectl get cluster <cluster-name> -o jsonpath='{.spec.connection.kubeconfig}' | base64 -d > /tmp/<cluster-name>-kubeconfig
Extension statusWhat does the opensearch skill do?
Use when installing or configuring the OpenSearch extension for KubeSphere, which provides distributed search and analytics engine for storing logs, events, auditing, and notification history
How do I install it?
Run `npx skills add kubesphere/kubesphere --skill opensearch --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From kubesphere/kubesphere, a repository with 17,016 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.