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

Scopes and Collections (Synchronization)

    XMLWordPrintable

Details

    • New Feature
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • None
    • 2.3.0
    • operator
    • None
    • 44: Completion 2.3, 46: Completion 2.3. bk maint, 48, 1: Recovery to productivity
    • 15

    Description

      If a user has created scopes and collections in a programmatic way or through REST APIs, 
      then if bucket is set to managed=true then CAO must discover all the scopes and collections existing under that bucket?

      Attachments

        Issue Links

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

          Activity

            The discovery process should not be a separate tool that will work only if the user activates the tool. This discovery process has to be running all the time by default and should be able to discover and keep the cluster in sync for all the scopes and collections created either dynamically/programmatically/through REST API or ones created through managed interface/approach of CAO scopes/collections. 

             

             

            roshani.sanghavi Roshani Sanghavi (Inactive) added a comment - The discovery process should not be a separate tool that will work only if the user activates the tool. This discovery process has to be running all the time by default and should be able to discover and keep the cluster in sync for all the scopes and collections created either dynamically/programmatically/through REST API or ones created through managed interface/approach of CAO scopes/collections.     

            Based on all the discussions since the last couple of weeks, here are more clearly written requirements which are expected from PM and pending for Dev acknowledgment,  needs further PM-Dev discussions to understand the complexities involved, cons or risks or efforts/rework required to do. [Sharing here for tracking purpose] -

            Pre-condition: For both scenarios: ‘cluster is running, has buckets, some scopes and collections. The bucket is managed and Scopes and collections are not managed. A developer, Jane, has access to the cluster’.

            Scenario 1 - we talked about today - Transitioning from Un-managed to Managed
            1. Jane adds something to her Java program to create scope foo, collection bar
            2. Beth, Administrator, sets the Managed flag to TRUE in YAML
            3. CAO automatically discovers the scopes and collections created in the Un-managed case and creates them in the Managed case, in the same cluster

            Scenario 2 - we have been talking about previously is - ‘Auto-discovery in Unmanaged’
            1. Jane adds something to her Java program to create scope foo, collection bar
            2. CAO automatically discovers the scopes and collections created in the Un-managed case and creates them
            3. Beth runs some kubectl get < options > to a directory to export the yaml

            roshani.sanghavi Roshani Sanghavi (Inactive) added a comment - Based on all the discussions since the last couple of weeks, here are more clearly written requirements which are expected from PM and pending for Dev acknowledgment,  needs further PM-Dev discussions to understand the complexities involved, cons or risks or efforts/rework required to do. [Sharing here for tracking purpose] - Pre-condition : For both scenarios: ‘cluster is running, has buckets, some scopes and collections. The bucket is managed and Scopes and collections are not managed. A developer, Jane, has access to the cluster’. Scenario 1 - we talked about today - Transitioning from Un-managed to Managed 1. Jane adds something to her Java program to create scope foo, collection bar 2. Beth, Administrator, sets the Managed flag to TRUE in YAML 3. CAO automatically discovers the scopes and collections created in the Un-managed case and creates them in the Managed case, in the same cluster Scenario 2 - we have been talking about previously is - ‘Auto-discovery in Unmanaged’ 1. Jane adds something to her Java program to create scope foo, collection bar 2. CAO automatically discovers the scopes and collections created in the Un-managed case and creates them 3. Beth runs some kubectl get < options > to a directory to export the yaml

            Build couchbase-operator-2.3.0-229 contains couchbase-operator commit 44077eb with commit message:
            K8S-2401: Resource Synchronization

            build-team Couchbase Build Team added a comment - Build couchbase-operator-2.3.0-229 contains couchbase-operator commit 44077eb with commit message: K8S-2401 : Resource Synchronization

            Arunkumar Senthilnathan  Prateek Kumar Roo Thorp looks like this another one got resolved fixed but I wanted to make sure changes, docs are tested and validated. 

            anil Anil Kumar (Inactive) added a comment - Arunkumar Senthilnathan    Prateek Kumar   Roo Thorp looks like this another one got resolved fixed but I wanted to make sure changes, docs are tested and validated. 

            Only docs validation for how-to guide pending

            arunkumar Arunkumar Senthilnathan added a comment - Only docs validation for how-to guide pending

            People

              arunkumar Arunkumar Senthilnathan
              roshani.sanghavi Roshani Sanghavi (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty