If setting the fsgroup recursively on a shared filesystem mount is
not desirable, the fsgroup capability on the flex driver
should first be disabled in the operator env vars. Now the driver
will apply the fsgroup only at the top level instead of
recursively for the entire shared filesystem.
Signed-off-by: travisn <tnielsen@redhat.com>
The flex settings cannot be passed to the driver with environment variables.
There is no context available for returning the flex settings except
that the flex driver will look in a config file in the same directory.
These settings must be valid or else the driver will return the default
settings.
Signed-off-by: travisn <tnielsen@redhat.com>
The flex driver no longer needs to check whether a kubelet
restart is needed or whether the namespace-specific driver
can be supported. The copy of k8s 1.13 types can also
be removed since we have updated to a newer k8s client.
Signed-off-by: travisn <tnielsen@redhat.com>
Introduce mount security mode for basic multi tenancy
Fixes#2164.
This adds three new parameters/options to StorageClass/flexvolume entry:
* `mountUser`
* `mountSecret`
* `mountSecretNamespace`
Signed-off-by: Alexander Trost <galexrt@googlemail.com>
As the `rookflex` volume plugin, the root command should be
`rookflex` instead of `rook`, else we'll get below confusing
message:
```
...bin/#./rookflex help
Rook Flex volume plugin
Usage:
rook [command]
Available Commands:
help Help about any command
init Initialize the volume plugin
mount Mounts the volume to the pod volume
unmount Unmounts the pod volume
```
Signed-off-by: Dennis Chen <dennis.chen@arm.com>
Update all K8s dependencies to the release-1.8 branches.
Added build and make file support for generating code.
Fixed our use of client-go to match changes in new release.