remove limits for pods

[sjenning]

@smarterclayton @brancz

follow on to my previous PR to make components run as Burstable, without limits

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: sjenning
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: s-urbaniak

If they are not already assigned, you can assign the PR to them by writing /assign @s-urbaniak in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[sjenning]

ugh, i did it again. these are generated files that i can't find the source for.

[sjenning]

doing this in openshift/prometheus-operator#20

[squat]

@sjenning this one is a little more tricky :p
These manifests are likewise all generated from jsonnet, however they come mostly from kube-prometheus, a distribution of monitoring components that we put together and are a dependency of this project [0]. The correct way to do this would be to write a mixin that removes limits for any object used in cluster monitoring operator. (We don’t want to remove the limits upstream in the kube-prometheus distro and other projects we are importing as they have valid use cases for limits). Please let me know if you need any help or want me to take over this and I can make a PR tomorrow.

[0]
https://github.com/openshift/cluster-monitoring-operator/blob/master/jsonnet/main.jsonnet#L1

[squat]

Note: kube-prometheus is being imported from the upstream repo, not the openshift fork
https://github.com/openshift/cluster-monitoring-operator/blob/master/jsonnet/jsonnetfile.json#L7

[squat]

finished this in #273