Skip to content

Conversation

@perdasilva
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 18, 2022
@openshift-ci openshift-ci bot requested review from exdx and kevinrizza August 18, 2022 13:59
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 18, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: perdasilva

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

The pull request process is described here

Details 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

@perdasilva perdasilva force-pushed the label_syncer_labelling branch from 9ad97e1 to 6a76a28 Compare August 18, 2022 14:00
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 18, 2022
@perdasilva perdasilva force-pushed the label_syncer_labelling branch from 6a76a28 to ebe976e Compare August 19, 2022 10:08
@perdasilva perdasilva force-pushed the label_syncer_labelling branch 2 times, most recently from 91120c2 to d6b8145 Compare August 19, 2022 10:12
Signed-off-by: perdasilva <[email protected]>
Upstream-repository: perdasilva
Upstream-commit: baaafa10f8d9f5c3251bfccb207c20bb84cdbc80
Signed-off-by: perdasilva <[email protected]>
@perdasilva perdasilva force-pushed the label_syncer_labelling branch from d6b8145 to 6679d14 Compare August 19, 2022 12:15
Copy link
Member

@joelanford joelanford left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks pretty good to me. Only question I have is whether its possible to hook and extra event handler into the existing CSV informer that we already use in the olm-operator?

If we could do that, we wouldn't need this extra informer.

// payload, as retrieved by listing the namespaces after a successful installation
// IMPORTANT: The Namespace openshift-operators must be an exception to this rule
// since it is used by OCP/OLM users to install their Operator bundle solutions.
var systemNSSyncExemptions = sets.NewString(
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I take it this is the exact same list as the label syncer's? Any chance we could get them to put that somewhere we could pull in? If not, how do we keep this up-to-date?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is - I just took it from their code for now. But yet, we definitely need to collapse into a single source of truth.

op.client,
namespace,
func(opts *metav1.ListOptions) {
// opts.LabelSelector = fmt.Sprintf("!%s", v1alpha1.CopiedLabelKey)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this commented out?

Copy link
Contributor Author

@perdasilva perdasilva Aug 19, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was a premature optimization. While it can help reduce the memory footprint, it means a 'not found' error when you try to get the namespace (you might still get csv events from csvs in namespaces that are culled). This felt a bit ambiguous and a potential source of confusion for the next developer. wdyt?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry, I confused myself here. The reason I commented this one out was because I was getting some strange behavior. I wasn't getting events for a non-openshift-* namespace...? I will try again to make sure though.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 19, 2022

@perdasilva: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/verify 6679d14 link true /test verify
ci/prow/unit-olm 6679d14 link true /test unit-olm

Full PR test history. Your PR dashboard.

Details

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. I understand the commands that are listed here.

@perdasilva perdasilva closed this Aug 22, 2022
perdasilva pushed a commit to perdasilva/operator-framework-olm that referenced this pull request Jan 15, 2025
Bumps [k8s.io/api](https://github.com/kubernetes/api) from 0.31.1 to 0.31.2.
- [Commits](kubernetes/api@v0.31.1...v0.31.2)

---
updated-dependencies:
- dependency-name: k8s.io/api
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Upstream-repository: api
Upstream-commit: 769c5e44dc3a5795c106d5e599b53d9a60b32891
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. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants