Open jeffvance opened 4 years ago
CSI uses well-defined key names in the storage class's parameters section. Example:
csi.storage.k8s.io/provisioner-secret-name csi.storage.k8s.io/provisioner-secret-namespace csi.storage.k8s.io/fstype
Even though the bucket library is not (yet?) part of the kubernetes organization, we can adopt similar names, especially in conjunction with other open issues that break the api.
Consider key names such as:
bucket.object-storage.k8s/secret-name bucket.object-storage.k8s/secret-namespace bucket.object-storage.k8s/region
+1 Before we do this, let's hammer down versioning.
hammer down versioning.
See #132
CSI uses well-defined key names in the storage class's parameters section. Example:
Even though the bucket library is not (yet?) part of the kubernetes organization, we can adopt similar names, especially in conjunction with other open issues that break the api.
Consider key names such as: