operator tektoncd-operator (0.72.0) #4647

piyush-garg · 2024-07-14T04:51:41Z

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)

Description about the managed Application and where to find more information
Features and capabilities of your Operator and how to use it
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 · 2024-07-14T04:52:25Z

@sm43,@vdemeester,@nikhil-thomas , 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 · 2024-07-14T04:52:26Z

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 · 2024-07-14T04:56:57Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),
⚠️	Value tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: owned CRD "manualapprovalgates.operator.tekton.dev" has an empty description
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

github-actions · 2024-07-14T04:59:46Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),
⚠️	Value tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: owned CRD "manualapprovalgates.operator.tekton.dev" has an empty description
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

piyush-garg · 2024-07-14T05:01:11Z

/hold

github-actions · 2024-07-14T05:05:48Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),
⚠️	Value tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: owned CRD "manualapprovalgates.operator.tekton.dev" has an empty description
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

piyush-garg · 2024-07-14T06:06:54Z

/hold cancel

github-actions · 2024-07-14T06:28:31Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: owned CRD "manualapprovalgates.operator.tekton.dev" has an empty description
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

github-actions · 2024-07-14T07:01:10Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

github-actions · 2024-07-14T07:15:27Z

This PR has changes outside of operators directory. Maintainers have to approve it.

piyush-garg · 2024-07-14T07:19:35Z

we need k8s 1.28 in CI

/hold

github-actions · 2024-07-14T07:37:20Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.0) 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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

jkandasa · 2024-07-14T16:55:12Z

cc @vdemeester

jkandasa · 2024-07-17T06:10:47Z

Hi @mporrato @Allda @tomasbakk our operator supported minKubeVersion is 1.28.0
Seems the CI rus with 1.27.2 kube version.
Can you please update the CI kube version to 1.28.0 or above?

Signed-off-by: Piyush Garg <[email protected]>

piyush-garg · 2024-08-10T09:19:00Z

/hold cancel

framework-automation · 2024-08-10T09:19:13Z

/merge possible

framework-automation · 2024-08-10T09:19:14Z

/merge possible

github-actions · 2024-08-10T09:43:08Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),
⚠️	Value tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

piyush-garg · 2024-08-10T12:25:32Z

/retest

openshift-ci · 2024-08-10T12:25:48Z

@piyush-garg: 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 · 2024-08-10T12:25:54Z

/hold

github-actions · 2024-08-10T12:26:06Z

/hold cancel

github-actions · 2024-08-10T12:50:39Z

Dear @piyush-garg,
Some errors and/or warnings were found while doing the check of your operator (tektoncd-operator/0.72.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 tektoncd-operator.v0.72.0: this bundle is using APIs which were deprecated and removed in v1.25. More info: https://kubernetes.io/docs/reference/using-api/deprecation-guide/#v1-25. Migrate the API(s) for cronjobs: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[24]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[21]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[22]"]),
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-lifecycle). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-cluster-operations). 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/
⚠️	Value tektoncd-operator.v0.72.0: unable to find the resource requests for the container: (tekton-operator-webhook). 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/
⚠️	Value tektoncd-operator.v0.72.0: CSV contains permissions to create CRD. An Operator shouldn't deploy or manage other operators (such patterns are known as meta or super operators or include CRDs in its Operands). It's the Operator Lifecycle Manager's job to manage the deployment and lifecycle of operators. Please, review the design of your solution and if you should not be using Dependency Resolution from OLM instead. More info: https://sdk.operatorframework.io/docs/best-practices/common-recommendation/

openshift-ci bot requested review from mporrato and tomasbakk July 14, 2024 04:51

github-actions bot assigned Allda and mporrato Jul 14, 2024

github-actions bot added the dco-failed label Jul 14, 2024

piyush-garg force-pushed the release_tekton_72 branch from 9c6a5b7 to 67c1573 Compare July 14, 2024 04:54

piyush-garg force-pushed the release_tekton_72 branch from 67c1573 to 431214c Compare July 14, 2024 04:59

github-actions bot removed the dco-failed label Jul 14, 2024

openshift-ci bot added the do-not-merge/hold label Jul 14, 2024

piyush-garg force-pushed the release_tekton_72 branch from 431214c to 9d8c8af Compare July 14, 2024 06:04

github-actions bot added package-validated installation-validated and removed installation-validated labels Jul 14, 2024

openshift-ci bot removed the do-not-merge/hold label Jul 14, 2024

github-actions bot removed the package-validated label Jul 14, 2024

piyush-garg force-pushed the release_tekton_72 branch from 9d8c8af to 97364f3 Compare July 14, 2024 06:39

piyush-garg force-pushed the release_tekton_72 branch from fa7da15 to 97364f3 Compare July 14, 2024 07:16

openshift-ci bot added the do-not-merge/hold label Jul 14, 2024

operator tektoncd-operator (0.72.0)

c287b33

Signed-off-by: Piyush Garg <[email protected]>

piyush-garg force-pushed the release_tekton_72 branch from 97364f3 to c287b33 Compare August 10, 2024 09:18

openshift-ci bot removed the do-not-merge/hold label Aug 10, 2024

github-actions bot added the package-validated label Aug 10, 2024

github-actions bot added the installation-validated label Aug 10, 2024

github-actions bot removed package-validated installation-validated labels Aug 10, 2024

openshift-ci bot added the do-not-merge/hold label Aug 10, 2024

openshift-ci bot removed the do-not-merge/hold label Aug 10, 2024

vdemeester approved these changes Aug 12, 2024

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

operator tektoncd-operator (0.72.0) #4647

operator tektoncd-operator (0.72.0) #4647

piyush-garg commented Jul 14, 2024 •

edited

Loading

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

jkandasa commented Jul 14, 2024

jkandasa commented Jul 17, 2024 •

edited

Loading

piyush-garg commented Aug 10, 2024

framework-automation commented Aug 10, 2024

framework-automation commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

piyush-garg commented Aug 10, 2024

openshift-ci bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

operator tektoncd-operator (0.72.0) #4647

Are you sure you want to change the base?

operator tektoncd-operator (0.72.0) #4647

Conversation

piyush-garg commented Jul 14, 2024 • edited Loading

New Submissions

Updates to existing Operators

Your submission should not

Operator Description must contain (in order)

Operator Metadata should contain

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

piyush-garg commented Jul 14, 2024

github-actions bot commented Jul 14, 2024

jkandasa commented Jul 14, 2024

jkandasa commented Jul 17, 2024 • edited Loading

piyush-garg commented Aug 10, 2024

framework-automation commented Aug 10, 2024

framework-automation commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

piyush-garg commented Aug 10, 2024

openshift-ci bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

github-actions bot commented Aug 10, 2024

piyush-garg commented Jul 14, 2024 •

edited

Loading

jkandasa commented Jul 17, 2024 •

edited

Loading