operator cluster-aas-operator (0.1.5)

[amisstea]

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

[amisstea]

Attn @rawagner

[github-actions]

@jtomasek,@mareklibra,@rawagner , 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]

Dear @amisstea,
Some errors and/or warnings were found while doing the check of your operator (cluster-aas-operator/0.1.5) against the entire suite of validators for Operator Framework with Operator-SDK version v1.30.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 clustertemplate.openshift.io/v1alpha1, Kind=ClusterTemplateSetup: provided API should have an example annotation
⚠️	Value clustertemplate.openshift.io/v1alpha1, Kind=Config: provided API should have an example annotation
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "clustertemplatesetup.clustertemplate.openshift.io" has an empty description
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "config.clustertemplate.openshift.io" has an empty description

[rawagner]

/retest

[github-actions]

/hold

[openshift-ci]

@rawagner: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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-sigs/prow repository.

[github-actions]

/hold cancel

[github-actions]

Dear @amisstea,
Some errors and/or warnings were found while doing the check of your operator (cluster-aas-operator/0.1.5) against the entire suite of validators for Operator Framework with Operator-SDK version v1.30.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 clustertemplate.openshift.io/v1alpha1, Kind=ClusterTemplateSetup: provided API should have an example annotation
⚠️	Value clustertemplate.openshift.io/v1alpha1, Kind=Config: provided API should have an example annotation
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "clustertemplatesetup.clustertemplate.openshift.io" has an empty description
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "config.clustertemplate.openshift.io" has an empty description

[rawagner]

/ok-to-test

[openshift-ci]

@rawagner: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/ok-to-test

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-sigs/prow repository.

[amisstea]

@rawagner do you have any clues as to what might be causing the CI failures? I see the controller manager pod is stuck on creation but otherwise I can't tell what the root cause is.

NAME                                                              READY   STATUS              RESTARTS   AGE
032a87f20f524f2ae801033aec7b419a1e79e44f8a5d7dceb818fc99ffgvmsk   0/1     Completed           0          14m
4858040cc62e08946163366ac7a2b19fd92030ef61522d70256b218b0fdjdsl   0/1     Completed           0          14m
argocd-operator-controller-manager-b6898f485-vxl4g                1/1     Running             0          14m
cluster-aas-operator-controller-manager-6fd44c4849-5vdf8          0/2     ContainerCreating   0          14m
test-operators-ocs-9q24j                                          1/1     Running             0          15m
test-operators-ocs-prod-9zl4w                                     1/1     Running             0          15m

I can pull the image I used (quay.io/stolostron/cluster-templates-operator:2.11.0-0c3131154065397d37e3b66ae635d7ea88650bf9) without issue.

[rawagner]

@amisstea Im not sure. Can you force-push to trigger the tests again ?

[github-actions]

Dear @amisstea,
Some errors and/or warnings were found while doing the check of your operator (cluster-aas-operator/0.1.5) against the entire suite of validators for Operator Framework with Operator-SDK version v1.30.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 clustertemplate.openshift.io/v1alpha1, Kind=ClusterTemplateSetup: provided API should have an example annotation
⚠️	Value clustertemplate.openshift.io/v1alpha1, Kind=Config: provided API should have an example annotation
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "clustertemplatesetup.clustertemplate.openshift.io" has an empty description
⚠️	Value cluster-aas-operator.v0.1.5: owned CRD "config.clustertemplate.openshift.io" has an empty description

[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.

[amisstea]

@rawagner please merge this when you get a chance.

[rawagner]

/hold

[rawagner]

/hold cancel

[framework-automation]

/merge possible

[framework-automation]

/merge possible