As an Admin, I want to have the possibility to configure a number of replicas for operands from the CR

[ibuziuk]

Is your task related to a problem? Please describe

After the removal of dependency on database, it is now possible to run multiple che-servers (and other operands) in parallel. As an Admin, I want to have the possibility to configure a number of replicas for operands from the CR.

Describe the solution you'd like

replicas CR property for each operand e.g.

spec:
  components:
    cheServer:
      deployment:
        replicas: 1
    dashboard:
      deployment:
        replicas: 1
    devfileRegistry:
      deployment:
        replicas: 1
    pluginRegistry:
      deployment:
        replicas: 1

By default, we can opt for 1, but admin can update the CR accordingly with explicit number of replicas for each operand

Describe alternatives you've considered

N / A

Additional context

Related to #7662

[ibuziuk]

@l0rd @tolusha could you please review the proposal? I do think we have the bandwidth to add it in the next 234 sprint but would be great to discuss it and prioritize for the future sprints

[l0rd]

Thanks @ibuziuk for opening this. I would rather add it under deployment as replica is a deployment spec:

spec:
  components:
    cheServer:
      deployment:
        replicas: 1
    dashboard:
      deployment:
        replicas: 1
    devfileRegistry:
      deployment:
        replicas: 1
    pluginRegistry:
      deployment:
        replicas: 1

[ibuziuk]

thank you for the review 👍 updated description

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

[achdmbp]

why is this closed ? has this been already addressed in a recent release?

[ibuziuk]

why is this closed? has this been already addressed in a recent release?

This issue is in the project backlog and we are currently working on supporting number of replicas for operands

[tolusha]

This issue has been solved in a different way.

This PR [1] prevents che-operator to reset the number of replicas on operands update.
To configure the number of replicas, use the HorizontalPodAutoscaler [2] [3]

[1] eclipse-che/che-operator#1804
[2] https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/
[3] https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale-walkthrough/

[ibuziuk]

@deerskindoll could you please review - eclipse-che/che-docs#2676

[ibuziuk]

blocked by Vale issue, docs PR can not be merged - https://issues.redhat.com/browse/RHDEVDOCS-5906