# Vector

Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension...

- Repository: https://github.com/kubesphere/kubesphere (17074 stars)
- Category: Engineering
- License: see repository
- Last updated: 2026-07-15
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add kubesphere/kubesphere --skill vector -g -a claude-code -y`
Codex: `npx skills add kubesphere/kubesphere --skill vector -g -a codex -y`
Cursor: `npx skills add kubesphere/kubesphere --skill vector -g -a cursor -y`
Gemini CLI: `npx skills add kubesphere/kubesphere --skill vector -g -a gemini-cli -y`

## Description

Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which provides data collection, transformation, and routing for observability data including logs, auditing, events, and notifications

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# WizTelemetry Data Pipeline (Vector)

## Overview

WizTelemetry Data Pipeline is an extension based on vector (https://vector.dev/) that provides the ability to collect, transform, and route observability data. It is a core dependency for other WizTelemetry extensions like Logging, Auditing, Events, and Notification.

## When to Use

- Installing or configuring the WizTelemetry Data Pipeline extension
- Setting up data collection for logs, auditing, events, and notifications
- Configuring Vector sinks (OpenSearch)
- Managing Vector agent components

## Installation

### Prerequisites

**REQUIRED: Complete all steps in order before generating InstallPlan.**

#### Step 1: Get Available Clusters and Confirm Target

**⚠️ CRITICAL: DO NOT proceed until target clusters are determined.**

**Step 1.1: Get available clusters**

```bash
kubectl get clusters -o jsonpath='{.items[*].metadata.name}'
```

**Step 1.2: Determine target clusters**

- If user **explicitly specified** target clusters in the request → Use those clusters directly, proceed to Step 2
- If user **did NOT specify** target clusters → Ask user to confirm which clusters to deploy to, then proceed to Step 2

**Ask user (if not specified):**
```
Available clusters: host, dev
Which clusters do you want to deploy Vector to?
```

#### Step 2: Get OpenSearch Endpoint and Credentials (MUST DO)

- If user **already provided** OpenSearch endpoint and credentials in the request → Use those directly, proceed to Step 3
- If user **did NOT provide** → **You MUST ask user** for OpenSearch endpoint and credentials

**Ask user for (if not provided):**

1. **OpenSearch endpoint URL** (required)
   - Example: `http://<node-ip>:30920` or `https://opensearch.example.com:9200`

2. **OpenSearch credentials** (required)
   - Username (default: `admin`)
   - Password

**DO NOT proceed to Step 3 until user provides both endpoint and credentials.**

#### Step 3: Get Latest Vector Version (if not provided by user)

The rest: https://github.com/kubesphere/kubesphere/blob/HEAD/skills/vector/SKILL.md