Uploaded image for project: 'OpenShift Service Mesh'
  1. OpenShift Service Mesh
  2. OSSM-3179

[Spike] Collect information to determine S/M/L deployment sizing

XMLWordPrintable

    • False
    • None
    • False

      Docs would like to start attempting to write Best Practices for various deployment sizing.  But first we need to talk to PM and Eng and determine best guesses for a small, medium, and large deployment.

       

      Acceptance Criteria-

      Schedule meeting with PM and Engineering to discuss.

      Come up with best guesses for sizing so that we can then determine minumum resource requirements:

      • number of nodes
      • number of clusters
      • control planes
      • namespaces
      • CPU, memory, and hardware recommendations
      • min and max number of pods based on usage spikes
      • blah de blah blah

            Unassigned Unassigned
            jstickler Julie Stickler (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: