- name
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,
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill vector -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill vector -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill vector -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add kubesphere/kubesphere --skill vector -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/kubesphere/kubesphere/tree/HEAD/skills/vectorFrom the publisher
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.
REQUIRED: Complete all steps in order before generating InstallPlan.
⚠️ 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
Ask user (if not specified):
Available clusters: host, dev
Which clusters do you want to deploy Vector to?
Ask user for (if not provided):
OpenSearch endpoint URL (required)
http://<node-ip>:30920 or https://opensearch.example.com:9200OpenSearch credentials (required)
admin)DO NOT proceed to Step 3 until user provides both endpoint and credentials.
MUST do this to get the latest version:
kubectl get extensionversions -l kubesphere.io/extension-ref=vector -o jsonpath='{range .items[*]}{.spec.version}{"\n"}{end}' | sort -V | tail -1
This outputs the latest version (e.g., 1.1.4). Note this down - you'll use it in the InstallPlan.
⚠️ IMPORTANT: Complete prerequisite steps (1-3) BEFORE this step.
⚠️ CRITICAL: InstallPlan metadata.name MUST be vector. DO NOT use any other name.
Based on your selections:
⚠️ CRITICAL: config field is YAML format. You MUST:
⚠️ CRITICAL: All placeholders MUST be replaced with actual values. DO NOT leave them as placeholders.
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: vector
spec:
extension:
name: vector
version: <VECTOR_VERSION> # From Step 3
enabled: true
upgradeStrategy: Manual
config: |
agent:
sinks:
opensearch:
auth:
strategy: basic
user: <OPENSEARCH_USER>
password: <OPENSEARCH_PASSWORD>
endpoints:
- <OPENSEARCH_ENDPOINT>
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Replace placeholders:
<VECTOR_VERSION>: From Step 2 (e.g., 1.1.4)<OPENSEARCH_ENDPOINT>: User-provided endpoint (e.g., http://<node-ip>:30920)<OPENSEARCH_USER>: User-provided username (default: admin)<OPENSEARCH_PASSWORD>: User-provided password<TARGET_CLUSTERS>: User-confirmed cluster names⚠️ DO NOT generate InstallPlan until all placeholders have real values.
After applying InstallPlan, you MUST wait for deployment to complete:
# Wait for Vector pods to be ready (on each cluster)
kubectl wait --for=condition=Ready pods -n kubesphere-logging-system -l app.kubernetes.io/instance=vector --timeout=300s
# Verify deployment status
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/instance=vector
Show deployment summary to user:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: vector
spec:
extension:
name: vector
version: <VECTOR_VERSION> # From Step 2
enabled: true
upgradeStrategy: Manual
config: |
agent:
sinks:
opensearch:
auth:
strategy: basic
user: <OPENSEARCH_USER>
password: <OPENSEARCH_PASSWORD>
endpoints:
- <OPENSEARCH_ENDPOINT>
exportMetrics:
enabled: true
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Example:
agent:
sinks:
opensearch:
endpoints:
- http://<node-ip>:30920
auth:
strategy: basic
user: admin
password: admin
tls:
verify: false
If Docker root directory is not /var/lib:
agent:
extraVolumes:
- name: docker-root
hostPath:
path: /path/to/docker
type: ''
extraVolumeMounts:
- name: docker-root
mountPath: /path/to/docker
# View extension installation status
kubectl get installplan vector
# View extension version
kubectl get extensionversions -l kubesphere.io/extension-ref=vector
# View all Vector pods
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/name=vector
# View agent pods
kubectl get pods -n kubesphere-logging-system -l app.kubernetes.io/name=vector,app.kubernetes.io/component=agent
# View agent logs
kubectl logs -n kubesphere-logging-system -l app.kubernetes.io/name=vector,app.kubernetes.io/component=agent --tail=100
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: vector
spec:
extension:
name: vector
version: <VECTOR_VERSION>
enabled: true
upgradeStrategy: Manual
config: |
agent:
sinks:
opensearch:
auth:
strategy: basic
user: <OPENSEARCH_USER>
password: <OPENSEARCH_PASSWORD>
endpoints:
- <OPENSEARCH_ENDPOINT>
clusterScheduling:
placement:
clusters:
- <TARGET_CLUSTERS>
Uninstall from all clusters:
kubectl delete installplan vector
Uninstall from specific cluster:
To remove Vector from a specific cluster, update the InstallPlan by removing that cluster from clusterScheduling.placement.clusters:
apiVersion: kubesphere.io/v1alpha1
kind: InstallPlan
metadata:
name: vector
spec:
extension:
name: vector
version: <VECTOR_VERSION>
enabled: true
upgradeStrategy: Manual
config: |
agent:
sinks:
opensearch:
auth:
strategy: basic
user: <OPENSEARCH_USER>
password: <OPENSEARCH_PASSWORD>
endpoints:
- <OPENSEARCH_ENDPOINT>
clusterScheduling:
placement:
clusters:
- <REMAINING_CLUSTERS> # Remove the cluster you want to uninstall from
installationMode: Multicluster:
agent (tag: agent) is deployed to all selected member clusters# View Vector configmap
kubectl get configmap -n kubesphere-logging-system -l app.kubernetes.io/name=vector
# View specific config
kubectl get configmap -n kubesphere-logging-system vector-config -o yaml
# Check if sinks are configured correctly
kubectl get secret -n kubesphere-logging-system vector-sinks -o yaml
© 2026 Skills Rack.
---name: vectordescription: Use when installing or configuring the WizTelemetry Data Pipeline (vector) extension for KubeSphere, which…---# skills/vector/SKILL.mdOverview
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
FAQ
Download skills/vector/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/kubesphere/kubesphere.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.