You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Use the submariner-operator Helm chart to deploy the Operator as the default deployment method throughout our CI, instead of subctl to deploy the Operator.
The current operator deploy method could be renamed subctl and run as an additional job in the submariner-operator repo.
Why is this needed:
To provide test coverage for both Helm and the Operator without adding a substantial number of extra jobs.
The text was updated successfully, but these errors were encountered:
Talking about this on the Automation Sync today, there didn't seem to be consensus that Helm+Operator should be the default throughout our CI. It should clearly be tested much more than it is throughout our CI, but folks pointed out that we currently recommend users use subctl constantly and so that might should be the default. I think discussions will continue as Helm gets fixed up. The topic of the number of jobs required for coverage wasn't considered.
This issue has been automatically marked as stale because it has not had activity for 60 days. It will be closed if no further activity occurs. Please make a comment if this issue/pr is still valid. Thank you for your contributions.
What would you like to be added:
Use the
submariner-operator
Helm chart to deploy the Operator as the default deployment method throughout our CI, instead ofsubctl
to deploy the Operator.The current
operator
deploy method could be renamedsubctl
and run as an additional job in the submariner-operator repo.Why is this needed:
To provide test coverage for both Helm and the Operator without adding a substantial number of extra jobs.
The text was updated successfully, but these errors were encountered: