operator [N] k8s-triliovault (5.0.2)

[trilio-ci-bot]

New operator bundle. Autogenerated PR

[github-actions]

Dear @trilio-ci-bot,
Some errors and/or warnings were found while doing the check of your operator (k8s-triliovault/5.0.2) 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 k8s-triliovault-stable.5.0.2: 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[12]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[14]"]),
⚠️	Value k8s-triliovault-stable.5.0.2: 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/
⚠️	Value k8s-triliovault-stable.5.0.2: csv.metadata.Name k8s-triliovault-stable.5.0.2 is not following the recommended naming convention: .v e.g. memcached-operator.v0.0.1

[github-actions]

Dear @trilio-ci-bot,
Some errors and/or warnings were found while doing the check of your operator (k8s-triliovault/5.0.2) 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 k8s-triliovault.5.0.2: 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[12]"])
⚠️	Value k8s-triliovault.5.0.2: 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/
⚠️	Value k8s-triliovault.5.0.2: csv.metadata.Name k8s-triliovault.5.0.2 is not following the recommended naming convention: .v e.g. memcached-operator.v0.0.1

[github-actions]

Dear @trilio-ci-bot,
Some errors and/or warnings were found while doing the check of your operator (k8s-triliovault/5.0.2) 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 k8s-triliovault.v5.0.2: 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]

Dear @trilio-ci-bot,
Some errors and/or warnings were found while doing the check of your operator (k8s-triliovault/5.0.2) 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 admissionregistration.k8s.io/v1, Kind=MutatingWebhookConfiguration: unsupported media type registry+v1 for bundle object
🐛	Value admissionregistration.k8s.io/v1, Kind=ValidatingWebhookConfiguration: unsupported media type registry+v1 for bundle object
⚠️	Value k8s-triliovault-stable.5.0.2: 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[12]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[14]"]),
⚠️	Value k8s-triliovault-stable.5.0.2: 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/
⚠️	Value k8s-triliovault-stable.5.0.2: csv.metadata.Name k8s-triliovault-stable.5.0.2 is not following the recommended naming convention: .v e.g. memcached-operator.v0.0.1