Scale up pulp resources in ops

What

Scaling up pulp resources in ops

• ingress-nginx replicacount 1 (default) -> 3
• pulp api
  • replicacount 10 -> 25
  • request cpu to 1, memory to 5Gi (Same as the web deployment for packagecloud ops deployment)
  • limit cpu to 4, memory to 5Gi (Same as the web deployment for packagecloud ops deployment)
• pulp worker
  • replicacount stayed the same 25 -> 25
  • request CPU to 1

Ref the pulp CRD definition for the keys used: https://github.com/pulp/pulp-operator/blob/main/config/crd/bases/repo-manager.pulpproject.org_pulps.yaml

Ref the ingress-nginx chart's controller deployent resource: https://github.com/kubernetes/ingress-nginx/blob/main/charts/ingress-nginx/templates/controller-deployment.yaml

Why

CPU is currently hitting 100 for api (dashboard)(api metric)

Links to relevant issues

https://gitlab.com/gitlab-org/build/team-tasks/-/issues/109