operator [CI] alloydb-omni-operator (1.4.0)

[jahnavi2k]

Thanks submitting your Operator. Please check 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 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 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 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

[github-actions]

@ack-bot , 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]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dear @jahnavi2k,
Some errors and/or warnings were found while doing the check of your operator (alloydb-omni-operator/1.4.0) against the entire suite of validators for Operator Framework with Operator-SDK version v1.36.0 and the command $ operator-sdk bundle validate <bundle-path> --select-optional suite=operatorframework.

Errors (:bug:) must be fixed while warnings (:warning:) are informative, and fixing them might improve the quality of your solution.

Type	Message
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=CreateStandbyJob: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=InstanceBackup: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=InstanceRestore: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=InstanceSwitchover: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=DeleteStandbyJob: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=Instance: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=Sidecar: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=BackupRepository: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=Failover: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=InstanceBackupPlan: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=LROJob: provided API should have an example annotation
⚠️	Value alloydbomni.internal.dbadmin.goog/v1, Kind=ReplicationConfig: provided API should have an example annotation
⚠️	Value alloydb-omni-operator.v1.4.0: unable to find the resource requests for the container: (kube-rbac-proxy). It is recommended to ensure the resource request for CPU and Memory. Be aware that for some clusters configurations it is required to specify requests or limits for those values. Otherwise, the system or quota may reject Pod creation. More info: https://master.sdk.operatorframework.io/docs/best-practices/managing-resources/

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[framework-automation]

/merge possible

[framework-automation]

/merge possible

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[github-actions]

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

[github-actions]

/hold

@ack-bot , Please note that ci.yml was changed.

• To approve follow instruction here

[github-actions]

Dockerfile or bundle.Dockerfile is added/changed. Note that for security reasons none of these files are going to be used when building bundle. Docker file will be generated and all label information is taken from annotations.yaml.

[jahnavi2k]

Hi @mporrato
Is there anything that can be done from our side to auto-merge PRs in the future? In the other repo - redhat-openshift-ecosystem/community-operators-prod#6352. we had specified automerge: true.

Regards
Jahnavi

[jahnavi2k]

Hi @mporrato @Allda @tomasbakk
Could you please help close this?

Regards
Jahnavi

[jahnavi2k]

Hi @mporrato @Allda @tomasbakk
Gentle reminder - could you please help us merge this?

Thanks and Regards
Jahnavi

[Allda]

@jahnavi2k If you want the PR to be auto-merged next time please add yourself to the list of reviewers https://github.com/k8s-operatorhub/community-operators/blob/main/operators/alloydb-omni-operator/ci.yaml#L3 This should auto-detect that you're an owner and merge it.

[framework-automation]

/merge possible

[github-actions]

Dear @jahnavi2k,
Your forked procject is not rebased

To fix this issue please rebase or execute following commands:

git clone https://github.com/jahnavi2k/community-operators /tmp/operators-repo
cd /tmp/operators-repo
git checkout origin/main
git remote add upstream https://github.com/k8s-operatorhub/community-operators -f
git pull --rebase upstream main

[jahnavi2k]

@jahnavi2k If you want the PR to be auto-merged next time please add yourself to the list of reviewers https://github.com/k8s-operatorhub/community-operators/blob/main/operators/alloydb-omni-operator/ci.yaml#L3 This should auto-detect that you're an owner and merge it.

Thanks @Allda!