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

Updated release of the Pelorus with it's pelorus-operator. #845

Merged
merged 1 commit into from
Feb 28, 2023

Conversation

mpryc
Copy link
Collaborator

@mpryc mpryc commented Feb 21, 2023

This is a new release 2.0.6 of the Pelorus with it's corresponding pelorus-operator version 0.0.3.

Describe the behavior changes introduced in this PR

This is just a source for the new release created using the following three calls:

$ ./scripts/create_release_pr -v 2.0.6
$ rm -rf pelorus-operator && mkdir pelorus-operator
$ ./scripts/create_pelorus_operator

This does not automatically create two container images required by the pelorus-operator:

quay.io/pelorus/pelorus-operator
quay.io/pelorus/pelorus-operator-bundle

To create those, log in to the quay.io account and then:

$ cd pelorus-operator/
$ make podman-build
$ make bundle-build
$ make podman-push
$ make bundle-push 

@redhat-cop/mdt

This is a new release 2.0.6 of the Pelorus with it's
corresponding pelorus-operator version 0.0.3.

Signed-off-by: Michal Pryc <mpryc@redhat.com>
@mateusoliveira43
Copy link
Collaborator

I would like that we address this issue #751 in operator schema. It is possible?

@mpryc
Copy link
Collaborator Author

mpryc commented Feb 23, 2023

I would like that we address this issue #751 in operator schema. It is possible?

No, because there are more caveats to consider to fix #751 and here it's a release that mostly aligns image versions / pelorus-operator.

@openshift-ci
Copy link

openshift-ci bot commented Feb 23, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mateusoliveira43

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 23, 2023
@mateusoliveira43
Copy link
Collaborator

As discussed, we need to automate the process, but this will be done in the next release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. dco-signoff: yes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants