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

Add NodeStageVolume to common CSI client lib #3905

Merged
merged 1 commit into from Sep 19, 2023

Conversation

fierlion
Copy link
Member

@fierlion fierlion commented Sep 13, 2023

Summary

This Adds the NodeStageVolume function to the csiclient library and extracts the connection setup into a helper function.

Implementation details

The client code is modeled after Kubernetes' CSI Client.

Testing

Tested via fierlion/NodeStageAltogether which includes the present CSI Client changes and CSI Driver updates from #3900 as well as hard-coded volume parameters in the task.go

New tests cover the changes: no

Description for the changelog

Add NodeStageVolume to common CSI client library.

Licensing

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@fierlion fierlion requested a review from a team as a code owner September 13, 2023 18:43
@fierlion fierlion changed the title Add NodeStageVolume to common csi client lib Add NodeStageVolume to common CSI client lib Sep 13, 2023
@fierlion fierlion force-pushed the fierlion/CSINodeStageClient branch 3 times, most recently from edadf33 to d768083 Compare September 13, 2023 20:26
@fierlion fierlion mentioned this pull request Sep 14, 2023
Realmonia
Realmonia previously approved these changes Sep 15, 2023
ecs-agent/csiclient/csi_client.go Outdated Show resolved Hide resolved
golang.org/x/tools v0.6.0
github.com/stretchr/testify v1.8.2
golang.org/x/net v0.13.0
golang.org/x/sys v0.10.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Do we care if these versions here (i.e., golang.org/x/sys, golang.org/x/tools) mismatch with the ones used in agent module? I wonder if it would be best practice/beneficial to use the same versions of these between both agent and ecs-agent modules.

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll have a follow-up tiny pr to fixup a couple of go module issues -- will add this as well. Good comment.

@fierlion fierlion force-pushed the fierlion/CSINodeStageClient branch 2 times, most recently from 7cb882b to b6d2aac Compare September 19, 2023 19:29
@fierlion fierlion merged commit dd25e3f into aws:dev Sep 19, 2023
40 checks passed
@fierlion fierlion deleted the fierlion/CSINodeStageClient branch September 19, 2023 23:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants