Choosing a Unique Package Name

The package name of your metadata bundle must be unique from your community operator. This section demonstrates changing an existing package name to satisfy this requirement.

Package name uniqueness (or lack of) can be a tripping point when certifying a community operator. Let's take a metadata bundle from a hypothetical community operator and examine the package.yaml file contents:

packageName: example
channels:
    - name: alpha
      currentCSV: example-operator-0.1.0

The typical convention is simply to add -certified as a suffix to the packageName like so:

packageName: example-certified
channels:
    - name: alpha
      currentCSV: example-operator-0.1.0

Now that your CSV and package yaml files are updated, you can proceed with bundling your metadata.