Skip to content

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Sep 12, 2025

Until downstream is ready to use the "app.kubernetes.io/name" selector, continue to use the "control-plane" selector in the tests.

Change the network-policies to use a "control-plane" selector (which is still on pods because the Deployment selector is immutable).

This includes a revert of "Use old and new pod selectors during kustomize-to-helm transition" This reverts #2214
This reverts commit 6e22e2b.

Description

Reviewer Checklist

  • API Go Documentation
  • Tests: Unit Tests (and E2E Tests, if appropriate)
  • Comprehensive Commit Messages
  • Links to related GitHub Issue(s)

@tmshort tmshort requested a review from a team as a code owner September 12, 2025 18:11
Copy link

netlify bot commented Sep 12, 2025

Deploy Preview for olmv1 ready!

Name Link
🔨 Latest commit 4c4684f
🔍 Latest deploy log https://app.netlify.com/projects/olmv1/deploys/68c466bcb78e3000086c929a
😎 Deploy Preview https://deploy-preview-2218--olmv1.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Until downstream is ready to use the "app.kubernetes.io/name" selector,
continue to use the "control-plane" selector in the tests.

Change the network-policies to use a "control-plane" selector (which is still
on pods because the Deployment selector is immutable).

This includes a revert of "Use old and new pod selectors during kustomize-to-helm transition"
This reverts operator-framework#2214
This reverts commit 6e22e2b.
@tmshort
Copy link
Contributor Author

tmshort commented Sep 12, 2025

If/When I want to go back to app.kubernetes.io/name selectors, I have to wait for downstream to use the helm config.

@tmshort
Copy link
Contributor Author

tmshort commented Sep 12, 2025

/approve

Copy link

openshift-ci bot commented Sep 12, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

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 Sep 12, 2025
Copy link

codecov bot commented Sep 12, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 72.00%. Comparing base (6e22e2b) to head (4c4684f).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2218      +/-   ##
==========================================
- Coverage   72.06%   72.00%   -0.06%     
==========================================
  Files          85       85              
  Lines        8401     8453      +52     
==========================================
+ Hits         6054     6087      +33     
- Misses       1943     1959      +16     
- Partials      404      407       +3     
Flag Coverage Δ
e2e 38.93% <ø> (-0.47%) ⬇️
experimental-e2e 46.18% <ø> (+0.03%) ⬆️
unit 56.82% <ø> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@grokspawn
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 12, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit e0a2e17 into operator-framework:main Sep 12, 2025
24 checks passed
@tmshort tmshort deleted the revert-e2e-fixes branch September 12, 2025 19:00
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. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants