mirrord-operator
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.
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "mirrord-operator" from https://skillstore.io/skills/metalbear-co-mirrord-operator.md and its manifest at https://skillstore.io/api/skills/metalbear-co-mirrord-operator/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "mirrord-operator". Plan a staging installation using an existing cloud API key Secret.
Expected outcome:
- Authentication: reference the existing Secret under cloud.apiKey.keyRef; its data key must be apiKey.
- Access: create chart roles only for required namespaces and review the proposed user bindings.
- Deployment: present Helm values and installation commands for approval before execution.
- Verification: check operator status and confirm the operator pod is running.
Using "mirrord-operator". Explain why a rotated cloud API key might not authenticate.
Expected outcome:
- Confirm that the configured Secret exists in the operator namespace.
- Check the Secret data key name and possible trailing newline without displaying the credential.
- Review relevant operator errors and confirm connectivity to the licensing service.
- Have the user update the Secret securely and approve any required deployment changes.
Using "mirrord-operator". What must change for an air-gapped deployment?
Expected outcome:
- Use an Enterprise offline license certificate or a self-hosted license server.
- Reference license material through Kubernetes Secrets rather than inline values.
- Mirror operator, agent, and enabled feature images into an accessible internal registry.
- Review trusted certificates, encrypted transport, and network requirements before installation.
Security Audit
High RiskMost 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.
Confirmed security concerns (14)
Show all 14 confirmed findings
Capability review items (4)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
๐ Network access (29)
โ๏ธ External commands (50)
๐ Filesystem access (1)
๐ Env variables (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/metalbear-co-mirrord-operator/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/metalbear-co-mirrord-operator?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/metalbear-co-mirrord-operator?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/metalbear-co-mirrord-operator/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/metalbear-co-mirrord-operator.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
metalbear-co. (2026). mirrord-operator security audit report (audit version 1) [Author version 2.14]. Skillstore. https://skillstore.io/skills/metalbear-co-mirrord-operator/audits/1BibTeX citation
@techreport{metalbear-co-metalbear-co-mirrord-operator-2026,
author = {metalbear-co},
title = {mirrord-operator security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/metalbear-co-mirrord-operator/audits/1},
note = {Author version 2.14}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "mirrord-operator security audit report (audit version 1)"
version: "2.14"
type: report
authors:
- name: "metalbear-co"
date-released: "2026-09-29"
url: "https://skillstore.io/skills/metalbear-co-mirrord-operator/audits/1"
identifiers:
- type: other
value: "skillstore:metalbear-co-mirrord-operator:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
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.
Try These Prompts
Explain the prerequisites for installing mirrord Operator in my staging cluster. List required tools, permissions, and licensing without running commands.
Prepare a mirrord Operator installation using an existing Kubernetes Secret for authentication. Show proposed values and commands, then wait for approval before changes.
My mirrord Operator cannot obtain its license after key rotation. Propose read-only checks, avoid displaying secrets, and request approval before corrective changes.
Review a multi-cluster mirrord rollout with preview replicas and PostgreSQL branching. Identify version requirements, RBAC limits, authentication risks, registry dependencies, and approval checkpoints.
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.
Avoid
- 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.
Frequently Asked Questions
Which AI tools can use this skill?
Does this skill include the mirrord Operator?
Can I use it without an existing license?
Does the trial work in an air-gapped cluster?
Should I give the agent my API key?
Will installation enable every feature?
Developer Details
Author
metalbear-coLicense
MIT
Author version
v2.14
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
bad9dafc37d1638cd29cb9bab06d5f8dbcd0f6c2
Maintenance freshness
9/30/2026
Usage
0 downloads ยท 0 views
File structure
๐ README.md
๐ references/
๐ helm-values.md
๐ troubleshooting.md
๐ values.yaml
๐ SKILL.md