Kubernetes Percona MySQL Operator

Deploys the Percona Operator for MySQL (Percona XtraDB Cluster) on a Kubernetes cluster using the official pxc-operator Helm chart (v1.18.0). The operator enables declarative lifecycle management of Percona XtraDB Cluster instances via PerconaXtraDBCluster custom resources, handling automated provisioning, scaling, backups, and failover of MySQL clusters.

What Gets Created

When you deploy a KubernetesPerconaMysqlOperator resource, OpenMCF provisions:

• Namespace — created only when createNamespace is true
• Helm Release — installs the pxc-operator Helm chart (v1.18.0) from the Percona Helm repository, deploying the operator pod with configurable CPU and memory resources; the Helm release is named {metadata.name}-pxc-operator
• Operator Pod — runs the Percona XtraDB Cluster operator, watching for PerconaXtraDBCluster custom resources and managing their lifecycle
• CRDs and RBAC — Custom Resource Definitions for PerconaXtraDBCluster 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-mysql-operator.yaml:

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

Deploy:

openmcf apply -f percona-mysql-operator.yaml

This installs the Percona MySQL Operator into the percona-system namespace with default resource limits (1000m CPU / 1Gi memory) and requests (100m CPU / 256Mi memory).

Configuration Reference

Required Fields

Optional Fields

Note on valueFrom: The namespace field is a StringValueOrRef type. You can provide a literal string value directly, or use valueFrom to reference the output of another OpenMCF resource. See the foreign key reference example below.

Examples

Default Operator Installation

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

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMysqlOperator
metadata:
  name: pxc-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesPerconaMysqlOperator.pxc-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 PXC instances, increase the operator's resource allocation to handle the additional reconciliation workload:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesPerconaMysqlOperator
metadata:
  name: prod-pxc-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.KubernetesPerconaMysqlOperator.prod-pxc-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: KubernetesPerconaMysqlOperator
metadata:
  name: shared-pxc-operator
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: staging.KubernetesPerconaMysqlOperator.shared-pxc-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
• KubernetesPostgres — alternative database operator for PostgreSQL workloads
• KubernetesHelmRelease — alternative for deploying Helm charts with custom configurations