Kubernetes Percona Mongo Operator

Deploys the Percona Operator for MongoDB on a Kubernetes cluster using its official Helm chart. The operator runs in cluster-wide mode, watching all namespaces for PerconaServerMongoDB custom resources, enabling declarative MongoDB lifecycle management across the cluster.

What Gets Created

When you deploy a KubernetesPerconaMongoOperator resource, OpenMCF provisions:

• Namespace — created only when createNamespace is true
• Helm Release — installs the psmdb-operator Helm chart (v1.20.1) from the Percona Helm repository, deploying the operator pod with configurable CPU and memory resources
• Operator Pod — runs in cluster-wide mode (watchAllNamespaces: true), monitoring all namespaces for PerconaServerMongoDB custom resources
• CRDs and RBAC — Custom Resource Definitions for PerconaServerMongoDB and associated ClusterRoles, ServiceAccounts, and bindings installed by the Helm chart

Prerequisites

• Kubernetes credentials configured via environment variables or OpenMCF provider config
• A Kubernetes namespace that already exists, or set createNamespace to true
• Helm-capable cluster — the cluster must support Helm chart installations (standard for all managed Kubernetes offerings)

Quick Start

Create a file percona-mongo-operator.yaml:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMongoOperator
metadata:
  name: my-percona-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesPerconaMongoOperator.my-percona-operator
spec:
  namespace: percona-system
  createNamespace: true

Deploy:

openmcf apply -f percona-mongo-operator.yaml

This installs the Percona MongoDB Operator into the percona-system namespace with default resource limits (1000m CPU / 1Gi memory) and requests (100m CPU / 256Mi memory), watching all namespaces for PerconaServerMongoDB custom resources.

Configuration Reference

Required Fields

Optional Fields

Examples

Default Operator Installation

Install the Percona MongoDB Operator with default resource allocations, creating the target namespace automatically:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMongoOperator
metadata:
  name: percona-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesPerconaMongoOperator.percona-operator
spec:
  namespace: percona-system
  createNamespace: true
  container:
    resources:
      limits:
        cpu: "1000m"
        memory: "1Gi"
      requests:
        cpu: "100m"
        memory: "256Mi"

Production Operator with Higher Resource Limits

For production clusters managing many MongoDB instances, increase the operator's resource allocation to handle the additional reconciliation workload:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMongoOperator
metadata:
  name: prod-percona-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.KubernetesPerconaMongoOperator.prod-percona-operator
spec:
  namespace: percona-system
  container:
    resources:
      limits:
        cpu: "2000m"
        memory: "2Gi"
      requests:
        cpu: "500m"
        memory: "512Mi"

Operator with Foreign Key Namespace Reference

Reference an OpenMCF-managed namespace instead of hardcoding the name. The valueFrom syntax resolves the namespace name from a KubernetesNamespace resource at deploy time:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMongoOperator
metadata:
  name: shared-percona-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: staging.KubernetesPerconaMongoOperator.shared-percona-operator
spec:
  namespace:
    valueFrom:
      kind: KubernetesNamespace
      name: operators-namespace
      field: spec.name
  container:
    resources:
      limits:
        cpu: "1000m"
        memory: "1Gi"
      requests:
        cpu: "200m"
        memory: "256Mi"

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• KubernetesNamespace — provides the target namespace via valueFrom reference
• KubernetesMongodb — deploys MongoDB instances managed by the Percona Operator installed by this component