✨ Promote Single Own Feature Gate AND Config spec in the CR to GA (OPRUN-4098)

[camilamacedo86]

Description

• Promote Single Own Feature Gate GA
• Promote the Config spec to the public/stable API. Without the spec.config.inline.watchNamespace field, there’s no place to declare which namespace the operator should watch, so the controller can only ever assume the default AllNamespaces behaviour. That’s why we need config available in the GA schema: it’s the user-facing knob that flips the controller into Single/Own namespace mode. Example:

  operator-controller/internal/operator-controller/applier/provider_test.go

  Lines 229 to 234 in 9eac616

  	Config: &ocv1.ClusterExtensionConfig{
  	ConfigType: ocv1.ClusterExtensionConfigTypeInline,
  	Inline: &apiextensionsv1.JSON{
  	Raw: []byte(`{"watchNamespace": "` + expectedWatchNamespace + `"}`),
  	},
  	},

Reviewer Checklist

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign kevinrizza for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[netlify]

✅ Deploy Preview for olmv1 ready!

Name	Link
🔨 Latest commit	64f8896
🔍 Latest deploy log	https://app.netlify.com/projects/olmv1/deploys/68ef530b6f92b40008ba30d5
😎 Deploy Preview	https://deploy-preview-2268--olmv1.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.00%. Comparing base (9eac616) to head (64f8896).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2268      +/-   ##
==========================================
+ Coverage   72.93%   73.00%   +0.06%     
==========================================
  Files          88       88              
  Lines        8743     8743              
==========================================
+ Hits         6377     6383       +6     
+ Misses       1951     1946       -5     
+ Partials      415      414       -1     

Flag	Coverage Δ
e2e	40.40% <ø> (+1.02%)	⬆️
experimental-e2e	46.79% <ø> (+0.07%)	⬆️
unit	58.11% <ø> (ø)

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.

[tmshort]

This seems to be conflated with #2267? i.e. this is changing the line for both the Webhook and Single/OwnNamespace features.

[camilamacedo86]

I thought the same when I was doing the PR. But let’s merge these in sequence: one first, then the other. The follow-up PR can be rebased and we’ll adjust the doc text—conflicts are only in the docs. I prefer keeping two PRs since they address different goals.

[camilamacedo86]

/hold

We might need to discuss more how to work with see: #2267 (comment)

So it si WIP

[camilamacedo86]

I think we can

/hold cancel

All comments are addressed
I am lookling for to see if we are satisfied with the default approach.

[tmshort]

Is there an order for this with respect to #2267?

[camilamacedo86]

Is there an order for this with respect to #2267?

No. I do think so.
But as we spoke, I think we will need to make changes here.
-> Do not enable feature flag by default
-> use the helm values to set those

/hold

until 🔨 meeting