oracle / zfssa-csi-driver Goto Github PK

Dependbot merge request does not build (#4). There are also a variety of newer versions available for dependent components (3rd and 4th party).

This branch will attempt to bring the driver to parity with the OLCNE version available (OLCNE 1.3 that is on 1.20.6 Kubernetes or the most current when this issue is worked on).

In some environments, a sidecar might be used that allows the credentials to not only be kept secret, but also be updated over time so they can be regularly rotated.

Currently, once the credentials are read and the token is created that wraps a created zfssa session, the credentials will never change and could start failing on a credential rotation.

I would like to change this so credentials can change but also clarify the distinction from the internal use of the "Token" and the notion of the ZFSSA "session".

The initial version of the driver does not implement volume cloning (https://v1-20.docs.kubernetes.io/docs/concepts/storage/volume-pvc-datasource/).

This should be achievable by

• creating a snapshot of the PVC referenced
• create the clone
• export the clone as a file system or LUN

This issue is 'generic' and may be split up if the filesystem path is substantially different from iscsi. For now, filesystem would be the priority since it would be common for boot images and home directories and such.

Come'on Oracle, get over it. You can do it. You can still sell the appliance and sell the support for it. Allow the kernel modules and cli tools, you can keep the GUI for sale with the appliance, orgs that buys that kind of stuff want support anyways so your sales will not be affected. It's time to let go. Please do it. Let Solaris go die its death, cherry pick ZFS and whatelse from it and that's it. I'm pretty sure you are in secret running it on Linux already internally.