issue

Currently csi and ccm controllers don't have limits or requests assigned to them.

This could create conditions where these pods use too much resources or don't have enough allocate for them

More info here

Acceptance criteria

• Allocate limits and requests to all essential cluster resources like these.

• Update the civogo lib to the last version
• Update the User Agent and set to civo-ccm/0.0.0

Feedback from helping a customer get this working:

I imagine it’s a fairly common use case to want to bind to a reserved IP at the point of creating the cluster (or later defining an Ingress manually).

It feels a little disjointed that it’s not picked up at the Ingress level.

Coming from GCP, a reserved IP can be bound in the same place that routing is defined.

We should review what GCP is doing and if we can make this user experience more intuitive