Skip to content

Conversation

gabrielalmeida
Copy link

Thanks submitting your Operator. Please check below list before you create your Pull Request.

New Submissions

Updates to existing Operators

  • Did you create a ci.yaml file according to the update instructions?
  • Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
  • Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
  • Have you tested an update to your Operator when deployed via OLM?
  • Is your submission signed?

Your submission should not

  • Modify more than one operator
  • Modify an Operator you don't own
  • Rename an operator - please remove and add with a different name instead
  • Modify any files outside the above mentioned folders
  • Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

  1. Description about the managed Application and where to find more information
  2. Features and capabilities of your Operator and how to use it
  3. Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

  • Human readable name and 1-liner description about your Operator
  • Valid category name1
  • One of the pre-defined capability levels2
  • Links to the maintainer, source code and documentation
  • Example templates for all Custom Resource Definitions intended to be used
  • A quadratic logo

Remember that you can preview your CSV here.

--

1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need

2 For more information see here

--

As per the Operator author @alexandrevilain's suggestion on alexandrevilain/temporal-operator#568 (comment) for contributing to updating the operator.

I've just bumped it to the latest version using the operatorhub automation script provided and marked the same checkboxes from previously published version PR.

Copy link
Contributor

@alexandrevilain,@ktenzer , please approve as you are original reviewer(s).

  • To add more contributors to ci.yaml follow instruction here.
  • To approve follow instruction here

@github-actions github-actions bot changed the title Update temporal-operator to 0.21.0 operator temporal-operator (0.21.0) Aug 15, 2025
@ktenzer
Copy link
Contributor

ktenzer commented Aug 15, 2025

/approve

@mantomas
Copy link
Collaborator

mantomas commented Sep 5, 2025

@gabrielalmeida you should put manifests and metadata directly to temporal-operator/0.21.0/ directory instead temporal-operator/0.21.0/bundle/ - the same as with other bundles, the bundle directory is unexpected and fail the validation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

5 participants