Skip to content
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

feat: move tolerations into LVMCluster.Spec #75

Merged
merged 2 commits into from
Jan 17, 2022
Merged

feat: move tolerations into LVMCluster.Spec #75

merged 2 commits into from
Jan 17, 2022

Conversation

nbalacha
Copy link
Contributor

This PR moves the tolerations field out of the deviceClass and into the main LVMCluster.Spec.
It also updates the tolerations in topolvm-node daemonset to match that of the vgmanager daemonset.

@nbalacha nbalacha requested review from leelavg and sp98 and removed request for leelavg January 17, 2022 15:01
This commit moves tolerations out of the individual deviceClasses
and into the main LVMCluster spec

Signed-off-by: N Balachandran <[email protected]>
The topolvm-node daemonset toleration will now be the same as
that of the vgmanager daemonset.

Signed-off-by: N Balachandran <[email protected]>
@@ -25,11 +25,13 @@ import (
// extractNodeSelectorAndTolerations combines and extracts scheduling parameters from the multiple deviceClass entries in an lvmCluster
func extractNodeSelectorAndTolerations(lvmCluster *lvmv1alpha1.LVMCluster) (*corev1.NodeSelector, []corev1.Toleration) {
var nodeSelector *corev1.NodeSelector
var tolerations []corev1.Toleration

tolerations := lvmCluster.Spec.Tolerations
Copy link
Contributor

@sp98 sp98 Jan 17, 2022

Choose a reason for hiding this comment

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

how about just returning lvmCluster.Spec.Tolerations from this method and not saving it in a variable first. The variable is never used.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

While that is a valid comment,I would like to address that in a separate PR

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 17, 2022
@sp98 sp98 self-requested a review January 17, 2022 15:29
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Jan 17, 2022

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: jmolmo, nbalacha, sp98

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

Needs approval from an approver in each of these files:

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

@nbalacha nbalacha merged commit 56de5eb into openshift:main Jan 17, 2022
@nbalacha nbalacha deleted the tolerations branch January 18, 2022 10:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants