operator dynatrace-operator (1.4.0)

[dt-team-kubernetes]

Signed-off-by: Dynatrace Team Kubernetes [email protected]

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

[rh-operator-bundle-bot]

Static test results

Status	Check	Message
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace.com/v1alpha2, Kind=EdgeConnect: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace.com/v1beta1, Kind=DynaKube: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace.com/v1beta3, Kind=DynaKube: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace.com/v1alpha1, Kind=EdgeConnect: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (dynatrace-operator.v1.4.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value : (dynatrace-operator.v1.4.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace-operator.v1.4.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[2].Rules[1]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[2].Rules[9]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[4].Rules[5]"])
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace-operator.v1.4.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[2].Rules[1]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[2].Rules[9]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[4].Rules[5]"])
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace-operator.v1.4.0: owned CRD "dynakubes.dynatrace.com" has an empty description
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace-operator.v1.4.0: owned CRD "edgeconnects.dynatrace.com" has an empty description
⚠️	check_osdk_bundle_validate_operator_framework	Warning: Value dynatrace-operator.v1.4.0: owned CRD "edgeconnects.dynatrace.com" has an empty description
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value dynatrace.com/v1beta1, Kind=DynaKube: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value dynatrace.com/v1beta3, Kind=DynaKube: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value dynatrace.com/v1alpha1, Kind=EdgeConnect: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value dynatrace.com/v1alpha2, Kind=EdgeConnect: provided API should have an example annotation
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (dynatrace-operator.v1.4.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : (dynatrace-operator.v1.4.0) csv.Spec.minKubeVersion is not informed. It is recommended you provide this information. Otherwise, it would mean that your operator project can be distributed and installed in any cluster version available, which is not necessarily the case for all projects.
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value dynatrace-operator.v1.4.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[2].Rules[1]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[2].Rules[9]" "ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[4].Rules[5]"])
⚠️	check_osdk_bundle_validate_operatorhub	Warning: Value : The "operatorhub" validator is deprecated; for equivalent validation use "operatorhub/v2", "standardcapabilities" and "standardcategories" validators
⚠️	check_required_fields	CSV does not define metadata.annotations.description
⚠️	check_using_fbc	File Based Catalog (FBC) is a new way to manage operator metadata. This operator does not use FBC. Consider migrating for better maintainability.

[rh-operator-bundle-bot]

Test artifacts: https://gist.github.com/rh-operator-bundle-bot/fab2ac871567858f5ae93fe27c667001

[rh-operator-bundle-bot]

Pipeline Summary

Pipeline: operator-hosted-pipeline
PipelineRun: operator-hosted-pipeline-run5djh2
Start Time: 2024-12-12 16:22:04+00:00

Tasks

Status	Task	Start Time	Duration
✔️	get-pr-number	2024-12-12 16:22:04+00:00	6 seconds
✔️	acquire-lease	2024-12-12 16:22:16+00:00	8 seconds
✔️	set-github-started-label	2024-12-12 16:22:33+00:00	8 seconds
✔️	set-github-status-pending	2024-12-12 16:22:45+00:00	7 seconds
✔️	set-env	2024-12-12 16:22:55+00:00	8 seconds
✔️	clone-repository	2024-12-12 16:23:11+00:00	46 seconds
✔️	clone-repository-base	2024-12-12 16:23:12+00:00	44 seconds
✔️	detect-changes	2024-12-12 16:24:06+00:00	49 seconds
✔️	yaml-lint	2024-12-12 16:25:02+00:00	45 seconds
✔️	check-permissions	2024-12-12 16:25:48+00:00	44 seconds
✔️	set-github-pr-title	2024-12-12 16:26:37+00:00	8 seconds
✔️	read-config	2024-12-12 16:26:49+00:00	49 seconds
✔️	resolve-pr-type	2024-12-12 16:27:45+00:00	6 seconds
✔️	apply-test-waivers	2024-12-12 16:27:59+00:00	41 seconds
✔️	content-hash	2024-12-12 16:28:48+00:00	42 seconds
✔️	certification-project-check	2024-12-12 16:29:37+00:00	46 seconds
✔️	get-organization	2024-12-12 16:30:29+00:00	43 seconds
✔️	get-pyxis-certification-data	2024-12-12 16:31:22+00:00	40 seconds
✔️	static-tests	2024-12-12 16:32:08+00:00	56 seconds
✔️	static-tests-results	2024-12-12 16:33:12+00:00	18 seconds
✔️	merge-registry-credentials	2024-12-12 16:33:37+00:00	19 seconds
✔️	digest-pinning	2024-12-12 16:34:02+00:00	50 seconds
✔️	verify-pinned-digest	2024-12-12 16:34:54+00:00	7 seconds
✔️	dockerfile-creation	2024-12-12 16:35:06+00:00	46 seconds
✔️	build-bundle	2024-12-12 16:35:52+00:00	55 seconds
✔️	make-bundle-repo-public	2024-12-12 16:36:48+00:00	8 seconds
✔️	get-supported-versions	2024-12-12 16:37:00+00:00	47 seconds
✔️	add-bundle-to-index	2024-12-12 16:37:50+00:00	3 minutes
✔️	make-index-repo-public	2024-12-12 16:41:42+00:00	7 seconds
✔️	get-ci-results-attempt	2024-12-12 16:41:52+00:00	14 seconds
✔️	preflight-trigger	2024-12-12 16:42:11+00:00	27 minutes
❌	evaluate-preflight-result	2024-12-12 17:09:56+00:00	47 seconds

Pipeline logs: https://gist.github.com/rh-operator-bundle-bot/6e4e415b4e8c2d8ccc9c4938dd4aa6c2

Troubleshooting

Please refer to the troubleshooting guide.

Run /pipeline restart operator-hosted-pipeline in case of pipeline failure to restart a pipeline.