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

Clarify order of operations in vertical scaling

    XMLWordPrintable

Details

    • 2.5.0 - The final countdown
    • 2

    Description

      Particularly in development/staging use cases, it's plausible that you'd want to increase the resource allocations for your pods, and increase the CB Quotas to take advantage of these. E.g.:

      Quota 256Mi -> 512Mi
      Mem request/limit 512Mi -> 1024Mi

      Conceptually, it makes sense to make these changes to the cluster resource and apply it, as the before and after states will both be valid. This fails however, as the operator is unaware of the dependancy between the two - it will try to swap in new pods with the higher resources, but it will also try to apply the new quota immediately. This will then fail, because the cluster is still made up of old pods and can't handle the new quota yet.

      It's potentially not the most common use case, but it's probably worth caveating. Maybe under https://docs.couchbase.com/operator/2.0/howto-couchbase-scale.html ?

      Attachments

        Issue Links

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

          Activity

            People

              justin.ashworth Justin Ashworth
              James Flather James Flather (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty