Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

operator [R] victoriametrics-operator (0.18.0) #5447

Conversation

AndrewChubatiuk
Copy link
Contributor

fix: removed reference to not existing version

@openshift-ci openshift-ci bot requested review from mporrato and tomasbakk December 18, 2024 18:15
@AndrewChubatiuk AndrewChubatiuk force-pushed the removed-reference-to-not-existing-version branch from 76eb673 to b0f6f88 Compare December 18, 2024 18:15
@github-actions github-actions bot changed the title victoriametrics-operator: removed reference to not existing version operator [R] victoriametrics-operator (0.18.0) Dec 18, 2024
@AndrewChubatiuk AndrewChubatiuk force-pushed the removed-reference-to-not-existing-version branch from ff529c4 to c191cce Compare December 18, 2024 18:24
Copy link
Contributor

Dear @AndrewChubatiuk,
Some errors and/or warnings were found while doing the check of your operator (victoriametrics-operator/0.18.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 vm-operator-vm-operator: invalid service account found in bundle. This service account vm-operator-vm-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV.
⚠️ Value : (victoriametrics-operator.v0.18.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.
⚠️ Value victoriametrics-operator.v0.18.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[43]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[11]"]),podsecuritypolicies: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[35]"]),
⚠️ Value victoriametrics-operator.v0.18.0: owned CRD "vmalertmanagerconfigs.operator.victoriametrics.com" has an empty description

Copy link
Contributor

Dear @AndrewChubatiuk,
Some errors and/or warnings were found while doing the check of your operator (victoriametrics-operator/0.18.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 vm-operator-vm-operator: invalid service account found in bundle. This service account vm-operator-vm-operator in your bundle is not valid, because a service account with the same name was already specified in your CSV. If this was unintentional, please remove the service account manifest from your bundle. If it was intentional to specify a separate service account, please rename the SA in either the bundle manifest or the CSV.
⚠️ Value : (victoriametrics-operator.v0.18.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.
⚠️ Value victoriametrics-operator.v0.18.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 podsecuritypolicies: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[35]"]),horizontalpodautoscalers: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[43]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[11]"]),
⚠️ Value victoriametrics-operator.v0.18.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[43]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[11]"]),podsecuritypolicies: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[35]"]),
⚠️ Value victoriametrics-operator.v0.18.0: owned CRD "vmalertmanagerconfigs.operator.victoriametrics.com" has an empty description

@AndrewChubatiuk AndrewChubatiuk force-pushed the removed-reference-to-not-existing-version branch from c191cce to d553f12 Compare December 18, 2024 18:57
Copy link
Contributor

Dear @AndrewChubatiuk,
Some errors and/or warnings were found while doing the check of your operator (victoriametrics-operator/0.18.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 : (victoriametrics-operator.v0.18.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.
⚠️ Value victoriametrics-operator.v0.18.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[43]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[11]"]),podsecuritypolicies: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[35]"]),
⚠️ Value victoriametrics-operator.v0.18.0: owned CRD "vmalertmanagerconfigs.operator.victoriametrics.com" has an empty description

@AndrewChubatiuk AndrewChubatiuk force-pushed the removed-reference-to-not-existing-version branch from d553f12 to 9c6a6c4 Compare December 18, 2024 19:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants