-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: Remove Helm deployment of NICClusterPolicy #1085
fix: Remove Helm deployment of NICClusterPolicy #1085
Conversation
@@ -1,49 +0,0 @@ | |||
{{- if and .Values.deployCR .Values.rdmaSharedDevicePlugin .deploy .Values.secondaryNetwork.deploy .Values.secondaryNetwork.multus.deploy .Values.secondaryNetwork.cniPlugins.deploy }} |
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.
Were these tests being used anywhere? They won't work after this change, but I'm wondering if this change means some loss in testing coverage.
fe2e617
to
89d85e0
Compare
89d85e0
to
100db60
Compare
Looks like the CI is broken due to authentication 🤔 |
Pull Request Test Coverage Report for Build 11349303874Details
💛 - Coveralls |
/retest-all |
Signed-off-by: killianmuldoon <[email protected]>
/retest-all |
100db60
to
8fc96f2
Compare
Also, docs repo will need update of https://github.com/Mellanox/network-operator-docs/blob/main/templates/helm.rst.gotmpl |
Remove the ability to create the NICClusterPolicy CR through helm.values. This feature has been deprecated for a number of releases and the documentation was updated to remove reference to this feature in the most recent release.
Users should instead use the helm package to install the Network Operator and configure the system by creating the NICClusterPolicy in a separate step.