Skip to content
This repository has been archived by the owner on Oct 22, 2024. It is now read-only.

set and test with default FS type #808

Merged
merged 4 commits into from
Nov 9, 2020
Merged

Conversation

pohly
Copy link
Contributor

@pohly pohly commented Nov 6, 2020

The updated test reveals that ownership changing fails when using a storage class without explicit FS type. This gets fixed by adding the --default-fstype parameter to external-provisioner (kubernetes-csi/external-provisioner#328 (comment)).

pohly added 4 commits November 6, 2020 13:12
The PV must have the filesystem specified for Kubernetes < 1.20 to
apply the FSGroup support (a heuristic in
Kubernetes). external-provisioner >= 2.0.0 only adds that field if it
knows about the default FS.

Fixes: intel#644
When running commands inside a pod it is better to first change into
/tmp before potentially extracting files, because the default
directory is / and that might not be writable when the container isn't
running as root.
This was broken for the default
FS (intel#644).
There are cases where it really matters whether the storage class
contains a FS
type (kubernetes-csi/external-provisioner#328 (comment)). To
cover that with our tests we need a storage class that has just the
defaults.

Explicitly setting reclaim policy and immediate binding also only
makes sense to show that those options exists, which is covered by
Kubernetes documentation. We better ensure that we really use the
defaults by not even setting those.
Copy link
Contributor

@avalluri avalluri left a comment

Choose a reason for hiding this comment

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

Looks good.

@avalluri avalluri merged commit 8fae276 into intel:devel Nov 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants