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 opentelemetry-operator (0.86.0) #3350

Conversation

opentelemetrybot
Copy link
Contributor

Release opentelemetry-operator 0.86.0.

cc @pavolloffay @frzifus @yuriolisa @jaronoff97 @VineethReddy02 @TylerHelmuth @swiatekm-sumo

Signed-off-by: opentelemetrybot <[email protected]>
@github-actions
Copy link
Contributor

@frzifus,@iblancasa,@yuriolisa,@pavolloffay , 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 github-actions bot changed the title Update the opentelemetry to 0.86.0 operator opentelemetry-operator (0.86.0) Oct 10, 2023
@github-actions
Copy link
Contributor

Dear @opentelemetrybot,
Some errors and/or warnings were found while doing the check of your operator (opentelemetry-operator/0.86.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 : (opentelemetry-operator.v0.86.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 opentelemetry-operator.v0.86.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[5]"]),poddisruptionbudgets: (["ClusterServiceVersion.Spec.InstallStrategy.StrategySpec.ClusterPermissions[0].Rules[13]"]),

@pavolloffay
Copy link
Contributor

/retest

@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2023

@pavolloffay: 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/test-infra repository.

@github-actions
Copy link
Contributor

/hold

@pavolloffay
Copy link
Contributor

/ok-to-test

@github-actions
Copy link
Contributor

/hold cancel

@openshift-ci
Copy link

openshift-ci bot commented Oct 11, 2023

@pavolloffay: 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/test-infra repository.

@framework-automation
Copy link
Collaborator

/merge possible

@framework-automation
Copy link
Collaborator

/merge possible

@github-actions
Copy link
Contributor

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

1 similar comment
@github-actions
Copy link
Contributor

Current PR can be merged automatically, but there is missing authorized-changes label. One can find out more info here.

@framework-automation
Copy link
Collaborator

/merge possible

@framework-automation framework-automation merged commit 668f031 into k8s-operatorhub:main Oct 17, 2023
23 of 25 checks passed
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.

8 participants