Resource Requests and Limits configuration segregation

[Read Only] Questions and Answers
1

INFORMATION

This topic is aimed for non-production environments only.
I already read @Pierre_Mavro’s response to “Fine gain control of resource requests and limits” by @prki on that specific topic.

ISSUE

Focusing on a cost-effective preproduction, development or staging environment, I’m stuck on how to deal configuring resource request and limits as Qovery is serving it in the console or API.
@Pierre_Mavro’s response is, in my opinion, legitimate only for production or preproduction environments. I’m pretty sure only few people do want a perfectly development environment ISO production (I would understand for preproduction though), because by definition, a development environment would hosts developers’ multiple test product stacks within that environment, whereas the production would only have one instance (replicated or not) of the main product.

I’m totally ok with a different scaling for a development environment in that case, but with the Qovery constraint on Request and Limits it would cost 1.5 environment by stack deployed. As a comparison, I have today many development stacks on a single VM with same capabilities as the cluster I’m configuring without any issues.

We would totally agree to experience latency on applications hosted in our development environment (but I’m pretty sure it won’t happen because the apps are really used from time to time).

Is there a workaround or any native solution to that issue?

2

Hello @Sryther
Indeed, for the various reasons mentioned in the article you attached, we do not provide this functionality.
However, now that we offer Helm services deployment, you have the opportunity to deploy and configure your applications with custom parameters.
I hope it helps.

3

However, now that we offer Helm services deployment, you have the opportunity to deploy and configure your applications with custom parameters.

That’s right, Helm could be an opportunity to configure effectively those parameters. Unfortunately, the customer I work for chose Qovery to avoid using such solutions because they don’t have human resources to maintain charts. It was kind of complicated to bring Terraform for Managed Databases creation (on Scaleway) for that reason.

Thanks anyway for your help! I think we’re going to make a call directly to explain the situation and find the best solution for my customer.

4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.