operator awx-operator (2.7.0)

[TheRealHaoLiu]

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

New Submissions

• Are you familiar with our contribution guidelines?
• Have you packaged and deployed your Operator for Operator Framework?
• Have you tested your Operator with all Custom Resource Definitions?
• Have you tested your Operator in all supported installation modes?
• Have you considered whether you want to use semantic versioning order?
• Is your submission signed?
• Is operator icon set?

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 of 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 name¹
• One of the pre-defined capability levels²
• 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.

--

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

² For more information see here

[openshift-ci]

Hi @TheRealHaoLiu. Thanks for your PR.

I'm waiting for a redhat-openshift-ecosystem member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rooftopcellist]

@TheRealHaoLiu CI is complaining because v4.10 is EOL.

  json:
    detail: Invalid semver in v4.10-v4.13n
    status: 400
    title: Bad Request
    trace_id: '0x657591ff53a1ad10a0471c2f1c232bee'
    type: about:blank
  msg: 'Status code was 400 and not [200]: HTTP Error 400: Bad Request'

Can you change the annotation in bundle/metadata/annotations.yaml to be:

annotations:
  com.redhat.openshift.versions: v4.11

[rooftopcellist]

It is probably complaining about the n at the end actually, not the fact that v4.10 is EOL. But none-the-less, can you change this to:

Suggested change

	com.redhat.openshift.versions: v4.10-v4.13n # Core bundle annotations.
	com.redhat.openshift.versions: v4.11 # Core bundle annotations.

That way it will support v4.11 and up, meaning the awx-operator will automatically be added to v4.14, and v4.15 when it comes out, etc.

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[framework-automation]

/merge possible