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

update crds for spiderpool dra feature #3527

Merged
merged 1 commit into from
Jun 21, 2024

Conversation

cyclinder
Copy link
Collaborator

Thanks for contributing!

What type of PR is this?

  • release/feature

What this PR does / why we need it:

update crds for spiderpool dra feature

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

@cyclinder cyclinder added the release/feature-new release note for new feature label May 27, 2024
Copy link

codecov bot commented May 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.16%. Comparing base (b6e4746) to head (63f7aa5).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main    #3527   +/-   ##
=======================================
  Coverage   81.16%   81.16%           
=======================================
  Files          50       50           
  Lines        4391     4391           
=======================================
  Hits         3564     3564           
  Misses        670      670           
  Partials      157      157           
Flag Coverage Δ
unittests 81.16% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

@@ -95,6 +99,10 @@ type SpiderIPvlanCniConfig struct {
// +kubebuilder:validation:Optional
Bond *BondConfig `json:"bond,omitempty"`

// +kubebuilder:default=false
// +kubebuilder:validation:Optional
EnableRdma bool `json:"enableRdma"`
Copy link
Collaborator

Choose a reason for hiding this comment

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

I am wondering whether there should be a new field called "rdmaResourceName" here

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done, maybe we can only use one field for this. If the value is empty, which means we don't use the rdma plugin. WDYT?

@@ -79,6 +79,9 @@ type SpiderMacvlanCniConfig struct {
// +kubebuilder:validation:Optional
Bond *BondConfig `json:"bond,omitempty"`

// +kubebuilder:validation:Optional
Copy link
Collaborator

Choose a reason for hiding this comment

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

there should be another filed enableRdma

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

maybe we can only use one field for this. If the value is empty, which means we don't use the rdma plugin. WDYT?

Copy link
Collaborator

@weizhoublue weizhoublue Jun 3, 2024

Choose a reason for hiding this comment

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

I do not think that way. Although, RdmaResourceName is a manual way. If no enableRdma, the user has no way to tell whether turn on it or not , when it supports to automatically inject resource name

and currently, sriov already has enableRdma field

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I'm ok with if we should keep consistent with sriov.

If no enableRdma, the user has no way to tell whether turn on it or not , when it supports to automatically inject resource name

ah, I think the resourceName is not to be automatically injected, configures it only manually, the Auto-injection means configuring the resourceName into the container's resources.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

follow your advice, done.

Signed-off-by: cyclinder <qifeng.guo@daocloud.io>
@cyclinder
Copy link
Collaborator Author

@weizhoublue ready to merge, please, this pr is pending spidernet-io/multus-cni#2.

@weizhoublue weizhoublue merged commit 5ad1b77 into spidernet-io:main Jun 21, 2024
53 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/feature-new release note for new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants