-
Notifications
You must be signed in to change notification settings - Fork 50
✨ Support for other Install strategies #802
✨ Support for other Install strategies #802
Conversation
Codecov ReportAttention:
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. |
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 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?
1790528
to
1939808
Compare
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. |
1939808
to
f68ed95
Compare
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]>
f68ed95
to
c4a3a1b
Compare
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: