-
Notifications
You must be signed in to change notification settings - Fork 31
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
Merge upstream tag v1.2.0 #86
Merge upstream tag v1.2.0 #86
Conversation
jmrodri
commented
Dec 16, 2020
**Description of the change:** centralize the code to manage the prerequisites to install OLM and Prometheus which are equals for all e2e tests **Motivation for the change:** - maintainability - reusability - remove code duplications across the e2e tests
* Deployment first commit * Deployment tests for all functions * Deployment tests for all functions updates * Deployment tests for all functions
…uild/push (#4081)
**Description of the change:** - Upgrade kb commit from f7a3b65dd250 to c993a2a221fe - Upgrade controller-runtime version from `v0.6.2` to `v0.6.3`. More info: https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.6.3 **Motivation for the change:** - Address bugfixes done in Kubebuilder so far - Solve tech-debts - Keep the projects aligned.
Modify `olm-status-descriptor-test` to not check the presence of `status` field in CR, instead validate only if status-descriptors are present in owned CRDs.
* Service test * Service test refined * Update internal/olm/operator/registry/configmap/service_test.go Co-authored-by: Camila Macedo <cmacedo@redhat.com>
…4086) * .cncf-maintainers: auto-generate expanded maintainers file for CNCF maintainers list * cncf-maintainers: fail generation if alias is not found
…found (#4089) Co-authored-by: Eric Stroczynski <estroczy@redhat.com>
… created APIs (#4105)
…ming to reduce flakes (#4118)
* update scorecard docs * update to mention kustomize files location Co-authored-by: jmccormick2001 <djm76262@gmail.com>
…125) Co-authored-by: jmccormick2001 <djm76262@gmail.com>
* Bump operator-framework/api to v0.3.18 * Bump operator-framework/api to v0.3.20
Co-authored-by: jmccormick2001 <djm76262@gmail.com>
/hold |
you can extract the operator-sdk binary from the sdk image built by the PR, for example,
you will now have the |
ansible-runner==1.3.4 \ | ||
ansible-runner-http==1.0.0 \ | ||
openshift~=0.10.0 \ | ||
ansible~=2.9 \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I know we're just merging commit wholesale but this needs to be pinned to 2.9.15 (see operator-framework/operator-sdk#4321). We can either wait for v1.2.1 or v1.3. Thoughts @jmrodri?
/ping @asmacdo
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Those aren't being used downstream. I probably need to compare the files on release/ansible
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@estroz I've compared the 2. The downstream has its own dockerfiles https://github.com/openshift/ocp-release-operator-sdk/tree/master/release I usually just compare them to see if there's anything significant that needs to be brought over. The versions of ansible etc, are all controlled by the packages in the downstream repo which are up to date.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cool, resolved.
@jmrodri I check the operatorsdk version is :./operator-sdk version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Since we are now patching the Makefile with the correct version. We shouldn't be passing in a new version from the Dockerfiles.
cdc6c02
to
e1e92b5
Compare
/test ci/prow/images |
@jmrodri: The specified target(s) for
Use In response to this:
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. |
/test images |
@emmajiafan not sure why the version isn't getting set. I updated the dockerfiles in this PR to set it directly. We could write a bug against it and address it later. I feel like this PR might be using cached images. Please try to test what you can |
@jmrodri Ok, will open a bug to trace it. And this pr merge a lot of codes ,so I will do a regression test about it and will cost about 2 days. |
@emmajiafan that is expected. It's a full 1.2.0 release from upstream. |
/approve |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: camilamacedo86, emmajiafan, estroz, jmrodri 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 |
/hold cancel |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |