Skip to content
This repository has been archived by the owner on Aug 12, 2024. It is now read-only.

✨ Support for other Install strategies #802

Merged

Conversation

varshaprasad96
Copy link
Member

Follow up of #772

This PR removes the requirement that AllNamespace mode should be supported always in a registry+v1 format.

It does so by:

  1. Adding a field to specify watch namespaces in BundleDeployment Spec.
  2. While converting from registryV1 to plain bundle, we now generate roles for all specified targetNamespaces which are being watched.

Copy link

codecov bot commented Jan 17, 2024

Codecov Report

Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (de8afc9) 26.29% compared to head (c4a3a1b) 35.27%.

Files Patch % Lines
internal/convert/registryv1.go 72.72% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #802      +/-   ##
==========================================
+ Coverage   26.29%   35.27%   +8.97%     
==========================================
  Files           9        9              
  Lines         810      808       -2     
==========================================
+ Hits          213      285      +72     
+ Misses        551      479      -72     
+ Partials       46       44       -2     

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

Copy link
Contributor

@everettraven everettraven left a comment

Choose a reason for hiding this comment

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

I think this looks good at a glance, but I do have a question - do we currently have a way to communicate the set of namespaces to watch via the deployment?

@varshaprasad96 varshaprasad96 force-pushed the support-watchnamespaces branch from 1790528 to 1939808 Compare January 17, 2024 18:27
@varshaprasad96
Copy link
Member Author

varshaprasad96 commented Jan 17, 2024

do we currently have a way to communicate the set of namespaces to watch via the deployment?

Which deployment are you referring to, could you elaborate pl? This PR introduces a spec field where watchnamespaces can specified while creating a BD (ref). It would then be added to cluster extension too.

@varshaprasad96 varshaprasad96 force-pushed the support-watchnamespaces branch from 1939808 to f68ed95 Compare January 17, 2024 18:35
@varshaprasad96 varshaprasad96 changed the title [Add] Support for other Install strategies ✨ Support for other Install strategies Jan 19, 2024
This PR removes the requirement that AllNamespace mode should be supported always in a registry+v1 format.

It does so by:

1. Adding a field to specify watch namespaces in BundleDeployment Spec.
2. While converting from registryV1 to plain bundle, we now generate roles for all specified targetNamespaces which are being watched.

Signed-off-by: Varsha Prasad Narsing <[email protected]>
@varshaprasad96 varshaprasad96 force-pushed the support-watchnamespaces branch from f68ed95 to c4a3a1b Compare January 19, 2024 17:40
@varshaprasad96 varshaprasad96 added this pull request to the merge queue Jan 19, 2024
Merged via the queue into operator-framework:main with commit 1018779 Jan 19, 2024
11 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants