Run any Skill in Manus with one click

couchbase-kubernetes

Stars4

Forks1

UpdatedMay 28, 2026 at 04:37

Deploy and operate Couchbase on Kubernetes using the Couchbase Autonomous Operator (CAO). Use whenever the user asks about Couchbase Autonomous Operator, CAO, CouchbaseCluster CRD, Couchbase on Kubernetes, Couchbase on EKS, Couchbase on GKE, Couchbase on AKS, Couchbase on OpenShift, Helm chart for Couchbase, CouchbaseBucket CRD, CouchbaseUser CRD, CouchbaseBackup CRD, CouchbaseReplicationRepresentation, server groups in Kubernetes, rack awareness in Kubernetes, persistent volumes for Couchbase, Couchbase pod resources, rolling upgrades via operator, Couchbase operator RBAC, Prometheus with CAO, or 'how do I run Couchbase on Kubernetes.' Distinct from couchbase-capella (managed Capella — no Kubernetes involved) and couchbase-upgrade (server binary upgrades outside Kubernetes). Use proactively when the user has a Kubernetes or OpenShift deployment requirement.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

celticht32

celticht32/Couchbase-Skills-for-Claude.ai

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

5 files

SKILL.md

readonly

name	couchbase-kubernetes
description	Deploy and operate Couchbase on Kubernetes using the Couchbase Autonomous Operator (CAO). Use whenever the user asks about Couchbase Autonomous Operator, CAO, CouchbaseCluster CRD, Couchbase on Kubernetes, Couchbase on EKS, Couchbase on GKE, Couchbase on AKS, Couchbase on OpenShift, Helm chart for Couchbase, CouchbaseBucket CRD, CouchbaseUser CRD, CouchbaseBackup CRD, CouchbaseReplicationRepresentation, server groups in Kubernetes, rack awareness in Kubernetes, persistent volumes for Couchbase, Couchbase pod resources, rolling upgrades via operator, Couchbase operator RBAC, Prometheus with CAO, or 'how do I run Couchbase on Kubernetes.' Distinct from couchbase-capella (managed Capella — no Kubernetes involved) and couchbase-upgrade (server binary upgrades outside Kubernetes). Use proactively when the user has a Kubernetes or OpenShift deployment requirement.
license	MIT

Couchbase on Kubernetes (Autonomous Operator)

A skill for deploying and operating Couchbase on Kubernetes using the Couchbase Autonomous Operator (CAO). CAO is a Level 5 Kubernetes Operator — it manages the full lifecycle of a Couchbase cluster as a set of Kubernetes custom resources.

Distinct from:

couchbase-capella — fully managed Capella (no Kubernetes to manage)
couchbase-upgrade — upgrading the Couchbase binary outside Kubernetes (or the planning layer for k8s upgrades)
couchbase-sizing — the capacity math applies equally; this skill covers the k8s-specific mechanics

When this skill applies

"How do I deploy Couchbase on Kubernetes?"
"How do I install the Couchbase Autonomous Operator?"
"How do I configure a CouchbaseCluster resource?"
"How do I configure rack awareness / AZ-awareness in Kubernetes?"
"How do I size persistent volumes for Couchbase pods?"
"How do I do a rolling upgrade via the operator?"
"How do I configure Prometheus monitoring with CAO?"
"How does the operator manage buckets, users, and backups?"
"How do I use the CAO Helm chart?"

Pick the right reference

Question	Read
"Installing CAO — Helm chart, namespaces, RBAC, admission controller"	`references/installation.md`
"CouchbaseCluster CRD — node topology, services, server groups, resources, storage"	`references/cluster-crd.md`
"Buckets, users, backups, XDCR as Kubernetes resources"	`references/supporting-crds.md`
"Operations — rolling upgrades, scaling, AZ awareness, Prometheus"	`references/operations.md`

Three core principles

Principle 1 — The operator reconciles, not you. Don't edit Couchbase directly through the UI or REST API when CAO is managing the cluster. CAO continuously reconciles the desired state (your CRDs) against the actual cluster state. Manual changes made outside the operator will be reverted on the next reconciliation cycle. All changes go through the CRD.

Principle 2 — Persistent volumes are the most important sizing decision. Data, Index, and Analytics nodes need persistent volumes that survive pod restarts. Size them generously — you can expand a PV online (if your storage class supports it) but you cannot shrink it. Use storage classes with allowVolumeExpansion: true and volumeBindingMode: WaitForFirstConsumer for AZ-aware scheduling.

Principle 3 — Server groups map to availability zones. Configure server groups that align with your Kubernetes node labels (topology zones, rack labels). CAO distributes pods across server groups using pod anti-affinity rules. Without server groups configured correctly, all Couchbase pods could land on nodes in the same AZ — defeating high availability.

Quick reference: CAO Custom Resource types

CRD	What it manages
`CouchbaseCluster`	The cluster itself — nodes, services, networking, TLS, server groups
`CouchbaseBucket`	Bucket lifecycle — creation, quota, type, replicas, TTL
`CouchbaseScope`	Scope within a bucket
`CouchbaseCollection`	Collection within a scope
`CouchbaseUser`	Local Couchbase users and their roles
`CouchbaseGroup`	User groups and role assignments
`CouchbaseRoleBinding`	Bind users to groups
`CouchbaseBackup`	Backup schedules and repositories
`CouchbaseBackupRestore`	Restore operations
`CouchbaseReplicationRepresentation`	XDCR remote cluster references and replications
`CouchbaseMemcachedBucket`	Memcached-type buckets
`CouchbaseEphemeralBucket`	Ephemeral (non-persistent) buckets

Supported Kubernetes distributions

CAO 2.9 (current) is certified for:

AWS EKS
Google GKE
Azure AKS
Red Hat OpenShift
Rancher (SUSE)
Vanilla upstream Kubernetes 1.27+

Version matrix

CAO version	Couchbase Server versions supported
2.9 (Dec 2025)	7.2, 7.6, 8.0
2.8	7.1, 7.2, 7.6
2.7	7.1, 7.2

Always match the CAO version to your Couchbase Server version. Check docs.couchbase.com/operator for the current support matrix.

Related skills

couchbase-sizing — node count, RAM, disk math before writing the CRD
couchbase-upgrade — upgrade planning, breaking changes, version path
couchbase-observability — Prometheus integration details (metrics endpoint, scrape config)
couchbase-security-hardening — TLS and RBAC patterns translate directly to CRD configuration
couchbase-backup-restore — backup strategy; CAO adds CouchbaseBackup CRD on top

More from this repository

same repository

couchbase-ai-applications

celticht32/Couchbase-Skills-for-Claude.ai

Design and build AI-powered applications on Couchbase, including RAG pipelines, vector search architecture, embedding strategies, and AI agent data patterns. Use whenever the user asks about RAG, retrieval-augmented generation, vector search for AI, Hyperscale Vector Index (HVI), Composite Vector Index (CVI), Search Vector Index (SVI), embedding pipelines, semantic search, AI agent memory, grounding LLMs with Couchbase, agentic data patterns, billion-scale vector search, multi-vector search, AI application architecture, or 'how do I build an AI app with Couchbase.' Distinct from couchbase-fts (which covers FTS index mechanics and query syntax) — this skill is about end-to-end AI application design: the data model, embedding pipeline, index type selection, retrieval strategy, and integration with LLM frameworks. Use proactively when the user is building AI features or has a use case involving language models, embeddings, or semantic retrieval.

2026-07-044

couchbase-coding-standards

celticht32/Couchbase-Skills-for-Claude.ai

Apply coding standards and a style guide for writing production application code against Couchbase, combining general software-engineering best practices (naming, functions, error handling, testing, docstrings, version control, code review, secrets hygiene) with Couchbase-specific conventions (SDK idioms, document-key naming, exception and retry handling, durability, parameterized SQL++, connection lifecycle). Use whenever the user asks about coding standards, code style, a style guide, clean code, naming conventions, structuring Couchbase application code, idiomatic SDK usage, how to write or review Couchbase code, code-review checklists, linting, formatting, testing Couchbase code, or best practices for writing Couchbase apps. Distinct from couchbase-app-integration (SDK mechanics: pooling, durability, scan consistency) and couchbase-data-modeling (document design) — this is the how-to-write-and-review-the-code layer on top of them. Use proactively when reviewing or authoring code that touches Couchbase.

2026-07-044

couchbase-columnar

celticht32/Couchbase-Skills-for-Claude.ai

Design and use Couchbase Capella Analytics (formerly Capella Columnar), the standalone columnar analytics database service on Capella. Use whenever the user asks about Capella Analytics, Capella Columnar, columnar analytics, an Analytics instance, Capella Analytics vs the operational Analytics Service, Analytics collections, links to operational data, Analytics SQL++, pricing, when to use standalone Capella Analytics vs the embedded Analytics Service, or 'I need to run analytical queries on my Couchbase data.' Distinct from the cb-analytics-* skills (which cover the Couchbase Analytics Service embedded in Couchbase Server / Capella operational clusters) — Capella Analytics is a separate, standalone columnar database product on Capella. Use proactively when the user needs OLAP-scale analytics, BI tool integration, or columnar storage for analytical workloads.

2026-07-044

couchbase-eventing

celticht32/Couchbase-Skills-for-Claude.ai

Design, deploy, and troubleshoot Couchbase Eventing functions. Use whenever the user asks about Eventing, eventing functions, JavaScript functions on document mutations, source bucket, metadata bucket, source keyspace, metadata keyspace, OnUpdate, OnDelete, cron triggers, curl() in eventing, N1QL in eventing, eventing deployment state (deployed / undeployed / paused), eventing worker count, DCP feed, Eventing service, admin_eventing_* tools, or 'how do I run code when a document changes.' Distinct from couchbase-mcp (calling the tools) and couchbase-app-integration (SDK-based change notification via DCP/Kafka). Use proactively when the user has a change-driven processing need: cache warming, audit logging, cross-collection sync, event publishing, or derived document generation.

2026-07-044

couchbase-fts

celticht32/Couchbase-Skills-for-Claude.ai

Design, build, and tune Couchbase Full Text Search (FTS) and vector search indexes. Use whenever the user asks about FTS indexes, Search service, text search, full-text search, fuzzy search, phrase search, wildcard search, regex search, geo search, geo-distance, geo-bounding-box, facets, scoring, boosting, analyzers, tokenizers, custom analyzers, language analyzers, type mappings, dynamic mappings, child mappings, FTS index design, FTS synonyms (8.x), vector search, kNN search, vector index, embedding search, hybrid search (FTS + vector), cb_fts_search, admin_fts_*, BLEVE, or 'how do I search text in Couchbase.' Distinct from couchbase-sqlpp-tuning (SQL++ index design) and couchbase-mcp (operating the tools). Use proactively when the user has a search use case — text relevance, semantic similarity, geo-proximity, or faceted navigation.

2026-07-044

couchbase-magma

celticht32/Couchbase-Skills-for-Claude.ai

Understand and tune the Magma storage engine in Couchbase. Use whenever the user asks about Magma, Magma storage engine, Couchbase storage backend, couchstore vs Magma, 128 vBuckets vs 1024 vBuckets, Magma compaction, Magma memory requirements, Magma disk layout, storage engine selection, when to use Magma vs couchstore, storageBackend bucket setting, numVBuckets bucket setting, or 'which storage engine should I use.' Distinct from couchbase-sizing (which has a brief Magma section in disk.md) — this skill covers Magma behavior, tradeoffs, and tuning in depth. Use proactively when the user is creating new buckets on 8.0 or is investigating storage-related performance issues.

2026-07-044

name	couchbase-kubernetes
description	Deploy and operate Couchbase on Kubernetes using the Couchbase Autonomous Operator (CAO). Use whenever the user asks about Couchbase Autonomous Operator, CAO, CouchbaseCluster CRD, Couchbase on Kubernetes, Couchbase on EKS, Couchbase on GKE, Couchbase on AKS, Couchbase on OpenShift, Helm chart for Couchbase, CouchbaseBucket CRD, CouchbaseUser CRD, CouchbaseBackup CRD, CouchbaseReplicationRepresentation, server groups in Kubernetes, rack awareness in Kubernetes, persistent volumes for Couchbase, Couchbase pod resources, rolling upgrades via operator, Couchbase operator RBAC, Prometheus with CAO, or 'how do I run Couchbase on Kubernetes.' Distinct from couchbase-capella (managed Capella — no Kubernetes involved) and couchbase-upgrade (server binary upgrades outside Kubernetes). Use proactively when the user has a Kubernetes or OpenShift deployment requirement.
license	MIT

Couchbase on Kubernetes (Autonomous Operator)

Distinct from:

couchbase-capella — fully managed Capella (no Kubernetes to manage)
couchbase-upgrade — upgrading the Couchbase binary outside Kubernetes (or the planning layer for k8s upgrades)
couchbase-sizing — the capacity math applies equally; this skill covers the k8s-specific mechanics

When this skill applies

"How do I deploy Couchbase on Kubernetes?"
"How do I install the Couchbase Autonomous Operator?"
"How do I configure a CouchbaseCluster resource?"
"How do I configure rack awareness / AZ-awareness in Kubernetes?"
"How do I size persistent volumes for Couchbase pods?"
"How do I do a rolling upgrade via the operator?"
"How do I configure Prometheus monitoring with CAO?"
"How does the operator manage buckets, users, and backups?"
"How do I use the CAO Helm chart?"

Pick the right reference

Question	Read
"Installing CAO — Helm chart, namespaces, RBAC, admission controller"	`references/installation.md`
"CouchbaseCluster CRD — node topology, services, server groups, resources, storage"	`references/cluster-crd.md`
"Buckets, users, backups, XDCR as Kubernetes resources"	`references/supporting-crds.md`
"Operations — rolling upgrades, scaling, AZ awareness, Prometheus"	`references/operations.md`

Three core principles

Quick reference: CAO Custom Resource types

CRD	What it manages
`CouchbaseCluster`	The cluster itself — nodes, services, networking, TLS, server groups
`CouchbaseBucket`	Bucket lifecycle — creation, quota, type, replicas, TTL
`CouchbaseScope`	Scope within a bucket
`CouchbaseCollection`	Collection within a scope
`CouchbaseUser`	Local Couchbase users and their roles
`CouchbaseGroup`	User groups and role assignments
`CouchbaseRoleBinding`	Bind users to groups
`CouchbaseBackup`	Backup schedules and repositories
`CouchbaseBackupRestore`	Restore operations
`CouchbaseReplicationRepresentation`	XDCR remote cluster references and replications
`CouchbaseMemcachedBucket`	Memcached-type buckets
`CouchbaseEphemeralBucket`	Ephemeral (non-persistent) buckets

Supported Kubernetes distributions

CAO 2.9 (current) is certified for:

AWS EKS
Google GKE
Azure AKS
Red Hat OpenShift
Rancher (SUSE)
Vanilla upstream Kubernetes 1.27+

Version matrix

CAO version	Couchbase Server versions supported
2.9 (Dec 2025)	7.2, 7.6, 8.0
2.8	7.1, 7.2, 7.6
2.7	7.1, 7.2

Always match the CAO version to your Couchbase Server version. Check docs.couchbase.com/operator for the current support matrix.

Related skills

couchbase-sizing — node count, RAM, disk math before writing the CRD
couchbase-upgrade — upgrade planning, breaking changes, version path
couchbase-observability — Prometheus integration details (metrics endpoint, scrape config)
couchbase-security-hardening — TLS and RBAC patterns translate directly to CRD configuration
couchbase-backup-restore — backup strategy; CAO adds CouchbaseBackup CRD on top