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

csi: provide CSI_ENDPOINT env var to plugins #12050

Merged
merged 2 commits into from
Feb 11, 2022
Merged

csi: provide CSI_ENDPOINT env var to plugins #12050

merged 2 commits into from
Feb 11, 2022

Conversation

tgross
Copy link
Member

@tgross tgross commented Feb 10, 2022

Fixes #11874 The CSI specification says:

The CO SHALL provide the listen-address for the Plugin by way of the CSI_ENDPOINT environment variable.

Note that plugins without filesystem isolation won't have the plugin dir bind-mounted to their alloc dir, but we can provide a path to the socket anyways. These still won't quite work until #11885 is complete.

I've also refactored to use an options struct for the plugin supervisor hook config. The parameter list was getting out of control and we use this pattern for similar task runner hooks (ex. template). That's in a second commit.

The CSI specification says:
> The CO SHALL provide the listen-address for the Plugin by way of the
`CSI_ENDPOINT` environment variable.

Note that plugins without filesystem isolation won't have the plugin
dir bind-mounted to their alloc dir, but we can provide a path to the
socket anyways.
The parameter list for configuring the plugin supervisor hook has
grown enough where is makes sense to use an options struct similiar to
many of the other task runner hooks (ex. template).
Copy link
Member

@shoenig shoenig left a comment

Choose a reason for hiding this comment

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

LGTM

@github-actions
Copy link

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backport/1.1.x backport to 1.1.x release line backport/1.2.x backport to 1.1.x release line theme/storage type/bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Set CSI_ENDPOINT environment variable
3 participants