Pelorus Operator v0.0.1 - Community Operator candidate #752
Conversation
|
More a question then a request: should the operator stuff live in a separated repo? |
We did talk about this previously and we may end up moving it to separate repo in the future. Currently it's easier to have it in same repo, because it uses helm-charts from pelorus one. |
|
Now that we will version it, I believe is important to check if the version is correct (I have already bumped a personal project from 0.0.1 to 0.1.1, for example) . I believe there is a better solution for this, but I use this in one project https://github.com/mateusoliveira43/cly/blob/main/tests/test_version.py#L84 And we should configure an action to automatically updated the operator in the marketplace as well, when version change occurs I would wait to have these two features before merging this PR |
|
/retest |
|
/hold |
openshift-ci
bot
added
the
do-not-merge/hold
|
This isn't yet passing the redhat-openshift-ecosystem/community-operators-prod#1967 Some labels are missing |
mpryc
force-pushed
the
operator_pelorus_quay_org
branch
from
497bec5 to
632446a
Compare
Pelorus Operator which is the candidate for the Community Operator To install: operator-sdk run bundle quay.io/pelorus/pelorus-operator-bundle:v0.0.1 --namespace pelorus Signed-off-by: Michal Pryc <mpryc@redhat.com>
mpryc
force-pushed
the
operator_pelorus_quay_org
branch
from
632446a to
f7b8f64
Compare
|
The upstream community operator PR (which is copy-paste from the generated bundle folder): redhat-openshift-ecosystem/community-operators-prod#1967 |
|
/retest |
|
/test 4.10-e2e-openshift |
|
/unhold |
openshift-ci
bot
removed
the
do-not-merge/hold
|
Looks like this is released? |
Yes, my hope was that this PR got merged prior to redhat-openshift-ecosystem/community-operators-prod#1967 but looks like the community operators got first in. If we can get this PR merged that would ensure we are 1-1 with what's in the community-operators-prod. I will propose some process to ensure we always get those two together. The community-operators-prod is at higher priority as there is number of CI jobs already implemented to ensure installation is correct for number of OCP releases. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: KevinMGranger 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 |
openshift-ci
bot
added
the
approved
Pelorus Operator which is the candidate for the Community Operator
To install:
operator-sdk run bundle quay.io/pelorus/pelorus-operator-bundle:v0.0.1 --namespace pelorusSigned-off-by: Michal Pryc mpryc@redhat.com
@redhat-cop/mdt