# Configure mirrord Operator for Kubernetes Teams

Team deployments require coordinated licensing, Kubernetes permissions, and feature configuration. This skill guides mirrord Operator setup and troubleshooting with Helm references and approval checkpoints.

## Install

```bash
npx skillstore add metalbear-co/mirrord-operator
```

## Metadata

- Status: approved
- Slug: metalbear-co-mirrord-operator
- Version: 2.14
- Author version: 2.14
- Skillstore revision: r1
- Version status: invalid
- Tree hash: defb5cb35dd0ac260d137f982d67956ff29b488b49580a9f112bf2b6bd8a50f4
- Author: metalbear-co
- GitHub username: metalbear-co
- License: MIT
- Repository: https://github.com/metalbear-co/skills/tree/a0ad7ca50ffb241a1c4f9c6a05d17661d5d658a5/skills/mirrord-operator
- Ref: bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: confirmation\_required
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: network, external\_commands, filesystem, env\_access
- Quality score: 38
- Quality tier: warning
- Public page: https://skillstore.pages.dev/skills/metalbear-co-mirrord-operator
- Manifest: https://skillstore.pages.dev/api/skills/metalbear-co-mirrord-operator/manifest

## Capabilities

- Guide Helm installation, upgrades, removal, and operator status checks.
- Explain cloud API key, Kubernetes Secret, Google Secret Manager, and offline licensing options.
- Identify Helm flags for queue splitting, database branching, preview environments, and multi-cluster operation.
- Provide configuration guidance for internal registries, OpenShift, GKE Autopilot, TLS, and chart-provided RBAC roles.
- Troubleshoot authentication failures, unavailable operators, certificate errors, resource limits, and interrupted sessions.
- Guide Enterprise trial registration after explicit approval and explain organization ownership requirements.

## Use Cases

- Deploy a Team Operator: Prepare a Helm installation with secret references, namespace access, selected features, and post-installation checks.
- Diagnose Session Access Failures: Identify operator availability, authentication, RBAC, and feature-flag problems using targeted status and log checks.
- Plan an Offline Deployment: Review Enterprise licensing, internal image registries, certificate provisioning, and restricted network requirements before rollout.

## Prompt Templates

### Check Installation Prerequisites

```
Explain the prerequisites for installing mirrord Operator in my staging cluster. List required tools, permissions, and licensing without running commands.
```

### Prepare a Helm Installation

```
Prepare a mirrord Operator installation using an existing Kubernetes Secret for authentication. Show proposed values and commands, then wait for approval before changes.
```

### Troubleshoot Operator Authentication

```
My mirrord Operator cannot obtain its license after key rotation. Propose read-only checks, avoid displaying secrets, and request approval before corrective changes.
```

### Review Multi-Cluster Deployment Controls

```
Review a multi-cluster mirrord rollout with preview replicas and PostgreSQL branching. Identify version requirements, RBAC limits, authentication risks, registry dependencies, and approval checkpoints.
```

## Limitations

- Execution requires installed Kubernetes, Helm, and mirrord tooling with appropriate cluster permissions.
- Team features require licensing; offline deployments require Enterprise licensing rather than the connected trial.
- Feature compatibility depends on operator, chart, and client versions; some detailed workflows reference separate skills.
- The skill provides guidance, not a security guarantee; credential examples and transport defaults require review before production use.

## Best Practices

- Confirm cluster context, namespaces, exact commands, and user approval before every cluster modification.
- Use Secret references, protect temporary credential files, and keep API keys out of agent output and committed values.
- Enable only required features, restrict access and branch images, and review TLS settings before production deployment.

## Anti Patterns

- Pasting authentication secrets into chat, command arguments, or committed Helm values.
- Starting trials or changing shared clusters without explicit user approval.
- Enabling preview environments or generic branching without reviewing permissions, image restrictions, and network access.

## Security Audit

- Audited at: 2026-09-29T21:50:06.411\+00:00
- Summary: Most alerts are false positives from Markdown formatting, YAML comments, and legitimate configuration references. Confirmed risks involve inline credentials, trial response exposure, and HTTP licensing; additional findings address transport security, database authentication, and excessive permissions. No evidence found of prompt injection or malicious intent; cluster changes and trial registration explicitly require user approval.

## Stats

- Views: 0
- Downloads: 2
- Favorites: 0
- Popularity score: 0