feat(overriding dashboard resources): Set resources on calico-dashboa…

[rene-dekker]

…rd-api

Users can now override the resources and/or limits on the calico-dashboard-api container in the manager deployment.

$kubectl patch manager tigera-secure -p '{"spec":{"managerDeployment":{"spec":{"template":{"spec":{"containers":[{"name":"calico-dash
  board-api","resources":{"limits":{"cpu":"522m","memory":"525Mi"},"requests":{"cpu":"115m","memory":"150Mi"}}}]}}}}}}' --type=merge
... (wait some time)
$ k get deploy -n calico-system calico-manager -o yaml | grep 522 -C 10
            command:
            - /usr/bin/dashboard-api
            - -ready
          failureThreshold: 3
          initialDelaySeconds: 5
          periodSeconds: 30
          successThreshold: 1
          timeoutSeconds: 5
        resources:
          limits:
            cpu: 522m
            memory: 525Mi
          requests:
            cpu: 115m
            memory: 150Mi
        securityContext:
          allowPrivilegeEscalation: false
          capabilities:
            drop:
            - ALL
          privileged: false

[caseydavenport]

LGTM - do we need any tests?

[rene-dekker]

There is an existing E2E that will start passing, see: https://tigera-delivery.semaphoreci.com/jobs/7376b444-e43c-4292-b61f-40e810fde1e4
It was already trying to update every container's resources and was already failing :)

[rene-dekker]

/merge-when-ready delete-branch

[marvin-tigera]

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and delete the branch after I've merged it.