vector-operator

Create and manage Vector operator CRDs for Kubernetes log collection and aggregation.

4|2|Updated Jun 1, 2026
One-click install
npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill vector-operator-aidas-dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: vector-operator
Source: https://github.com/Aidas-dev/k8s-agent-skills/tree/main/skills/vector-operator
Command: npx skills add https://github.com/Aidas-dev/k8s-agent-skills --skill vector-operator-aidas-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Configuring Vector log pipelines on Kubernetes requires manually managing DaemonSets, Deployments, and complex Vector configuration files. This Skill provides the knowledge to declaratively manage Vector agents, aggregators, and pipelines through the kaasops Vector operator CRDs, with automatic routing of pipeline configs to the right component. ## Core Features & Use Cases - CRD Management: Create and configure Vector (DaemonSet agent), VectorAggregator (Deployment), VectorPipeline, ClusterVectorPipeline, and ClusterVectorAggregator resources under the observability.kaasops.io/v1alpha1 API. - Auto-Routing Logic: Understand how pipelines with kubernetes_logs or file sources route to agents while network sources (kafka, socket, http_server) route to aggregators. - Use Case: Deploy a production log pipeline that collects Kubernetes pod logs from namespaces labeled environment=production, enriches them with VRL remap transforms, and ships them to Elasticsearch with credentials stored in Secrets. ## Quick Start Ask the agent to create a VectorPipeline that collects kubernetes_logs and ships them to Elasticsearch, along with the matching Vector agent DaemonSet CR.

Frequently Asked Questions about vector-operator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Vector on Kubernetes with an operator?▼

Install the kaasops vector-operator via Helm into the vector-system namespace, then create a Vector CR for the DaemonSet agent and a VectorAggregator CR for the Deployment. The operator reconciles these into running Vector workloads with generated configuration.

How do I collect Kubernetes pod logs with Vector operator?▼

Create a VectorPipeline with a kubernetes_logs source and your desired sinks such as Elasticsearch or Kafka. The operator auto-routes pipelines with kubernetes_logs or file sources to the Vector agent DaemonSet and merges the config automatically.

What is the difference between VectorPipeline and ClusterVectorPipeline?▼

VectorPipeline is namespace-scoped and only applies to Vector instances in the same namespace. ClusterVectorPipeline is cluster-scoped and can collect sources from any namespace, making it suitable for cluster-wide log collection.

Why is my VectorPipeline config not being applied?▼

Pipelines only apply when a matching Vector or VectorAggregator exists in the same namespace. Also check source-type routing: kubernetes_logs and file sources go to agents, while network sources like kafka or socket go to aggregators.

Does uninstalling the vector-operator Helm chart delete my Vector resources?▼

Yes, if createCRD is true (the default), running helm uninstall deletes the CRDs, which removes all Vector custom resources. Set createCRD to false and manage CRDs externally to avoid this.