Skip to content

Question: Can Percona add a second entry for Percona Operators alongside existing Percona Server for MySQL? #4825

Description

@edithturn

Hi! I'm a CNCF Ambassador working on the Percona Operators team. Percona is a Silver CNCF member currently listed in the Database category with Percona Server for MySQL.

I'd like to explore adding a separate entry for Percona Operators; four open source Kubernetes Operators for MongoDB, MySQL, and PostgreSQL and XtraDB Cluster. We'd use additional_repos to reference all four operator repositories under one entry, and all four operators share a single unified logo.

Here is the proposed entry:

- item:
    name: Percona Kubernetes Operators
    description: >-
      Open source Percona Kubernetes Operators for managing MongoDB, MySQL,
      PostgreSQL and XtraDB Cluster databases on Kubernetes.
    homepage_url: https://www.percona.com/software/percona-kubernetes-operators
    repo_url: https://github.com/percona/percona-server-mongodb-operator
    additional_repos:
      - repo_url: https://github.com/percona/percona-postgresql-operator
      - repo_url: https://github.com/percona/percona-xtradb-cluster-operator
      - repo_url: https://github.com/percona/percona-server-mysql-operator
    logo: percona-operators.svg
    crunchbase: https://www.crunchbase.com/organization/percona
    extra:
      tag: app-delivery

Would this qualify as a second entry alongside the existing listing?
Or would you prefer we replace it?

I would greatly appreciate your guidance on the best approach before I proceed with a PR. Thank you for your support!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions