
Vector
Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension...
Install
npx skills add kubesphere/kubesphere --skill vector -g -a claude-code -y- Repository
- kubesphere/kubesphere17.1k
- Category
- Engineering
- Updated
- 4mo ago
- License
- See repository
- Context cost
- Mediumabout 2,566 tokens
- Runs scripts
- No, instructions only
What it does
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
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
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):
-
OpenSearch endpoint URL (required)
- Example:
http://<node-ip>:30920orhttps://opensearch.example.com:9200
- Example:
-
OpenSearch credentials (required)
- Username (default:
admin) - Password
- Username (default:
DO NOT proceed to Step 3 until user provides both endpoint and credentials.
