Add resource request and limits to Backstage Application and Local DB the Backstage CR Spec

[jianrongzhang89]

This issue to resource request and limits to Backstage Application and Local DB the Backstage CR Spec so that the user can override them via the CR:

• memory and CPU request and limit to Backstage Application
• memory and CPU request and limit to Local DB
• storage size for Local DB

[gazarenkov]

Duplicates
https://issues.redhat.com/browse/RHIDP-1153
#185

[jianrongzhang89]

Duplicates https://issues.redhat.com/browse/RHIDP-1153 #185

@#185 is for the resource limits/requests in the default configuration. This one to add the parameters to the Backstage CR.

[gazarenkov]

Duplicates https://issues.redhat.com/browse/RHIDP-1153 #185

@#185 is for the resource limits/requests in the default configuration. This one to add the parameters to the Backstage CR.

I am not sure if we need to extend CR this way, because:

• more likely user has no idea about these numbers (it is not easy to estimate) so normally it should be configured by Admin, cluster wide.
• it can be set up as a part of raw configuration if really needed

[jianrongzhang89]

Duplicates https://issues.redhat.com/browse/RHIDP-1153 #185

@#185 is for the resource limits/requests in the default configuration. This one to add the parameters to the Backstage CR.

I am not sure if we need to extend CR this way, because:

• more likely user has no idea about these numbers (it is not easy to estimate) so normally it should be configured by Admin, cluster wide.
• it can be set up as a part of raw configuration if really needed

One use case I can think of is this will allow the admins to easily deploy two instances of backstage (one for testing and one for production, for instance) with different resource limits.

In addition, we should consider what happens when the operator version is upgraded which may reset the limits from the new release. If the user configures them in their custom resources, they are less concerned about the upgrades.

[nickboldt]

As part of the migration from janus-idp to redhat-developer in https://issues.redhat.com/browse/RHIDP-1021, this will be tracked in https://issues.redhat.com/browse/RHIDP-1206