Uploaded image for project: 'Couchbase Kubernetes'
  1. Couchbase Kubernetes
  2. K8S-556

Couchbase-Operator Support for non-dynamic provisioning of persistent volumes

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 1.2.0
    • operator

    Description

      Currently the Couchbase operator supports only provisioning via Storage classes which is dynamic in nature. We will need to support the scenarios where the storage classes are not available (For example: NFS) and where a user will create PVs and PVCs manually.

       

       

      Attachments

        No reviews matched the request. Check your Options in the drop-down menu of this sections header.

        Activity

          Description for release notes:

          Summary: Known Issue Only dynamic volume provisioning via storage classes is supported.

          eric.schneider Eric Schneider (Inactive) added a comment - Description for release notes: Summary: Known Issue Only dynamic volume provisioning via storage classes is supported.

          Removing the check for storageclass since the the volumeClaimTemplates can be evaluated without them as is the case here.  Also worth noting, this spec actually requires 9 claimTemplates since there is a request for 3 nodes each mounting 3 volumes.

          tommie Tommie McAfee added a comment - Removing the check for storageclass since the the volumeClaimTemplates can be evaluated without them as is the case here.  Also worth noting, this spec actually requires 9 claimTemplates since there is a request for 3 nodes each mounting 3 volumes.

          After some quick experimentation it's best to just create a 'local' storageclass, this way users can create as many PV's they want and tag them with the class.  Verified that the use case here works for current codebase with the following storageclass:

          apiVersion: storage.k8s.io/v1
          kind: StorageClass
          metadata:
            name: slow
          provisioner: local 
          volumeBindingMode: Immediate 

           

           

          tommie Tommie McAfee added a comment - After some quick experimentation it's best to just create a 'local' storageclass, this way users can create as many PV's they want and tag them with the class.  Verified that the use case here works for current codebase with the following storageclass: apiVersion: storage.k8s.io/v1 kind: StorageClass metadata:   name: slow provisioner: local  volumeBindingMode: Immediate    
          simon.murray Simon Murray added a comment -

          Tommie can we close this enhancement out?  Will make Lynn a lot happier (and the meeting shorter) if we only have the one

          simon.murray Simon Murray added a comment - Tommie can we close this enhancement out?  Will make Lynn a lot happier (and the meeting shorter) if we only have the one

          Yep, thanks for reminder

          tommie Tommie McAfee added a comment - Yep, thanks for reminder

          People

            tommie Tommie McAfee
            sindhura.palakodety Sindhura Palakodety (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Gerrit Reviews

                There are no open Gerrit changes

                PagerDuty