Allow specifying resource requirements in docker-compose service labels

[MaxCWhitehead]

Goals / Usage:

• Be able to define default resource requirements per service
• Be able to override these per env
• Primary usage is configuring for nginx-php services (nginx + php containers in shared pod, should support linked services)

Specified as service labels in lagoon project yml:

  php:
    labels:
      lagoon.type: nginx-php-persistent
      lagoon.name: nginx-php
      
      # Set default resources for php service
      lagoon.resources.requests.cpu: 20m
      lagoon.resources.limits.cpu: 200m
      
      # Override on main branch
      lagoon.resources.override-branch.main.requests.cpu: 400m
      lagoon.resources.override-branch.main.limits.cpu: 400m

Changes:

• Update Resources type to contain memory/cpu resources/requests
• Add Resources to ServiceValues (BuildValues templating input now may store resources per service)
• Update composeToServiceValues to read service labels to set resources in ServiceValues
  • Prioritizes branch overrides, then uses label for service if specified
• Update GenerateDeploymentTemplate To override resource requirements on container spec if present in ServicValues

Tests added

The tests are a bit rough and possibly hard to grok (copy and pasted from similar and tweaked to test this functionality. But what I tried to cover:

• Ensuring that original default ServiceType resource values are used if not overridden
• ServiceValue.Resources overrides BuildValues.Resources (if overrides are set)
• Testing compose labels are plumbed into ServiceValues correctly
  • Testing that branch override service labels override default resource labels in docker-compose
• Testing resources templated correctly in deployment manifest from BuildValues/ServiceValues

[gchaix]

Let's build it and give it a spin!