Add suport for kubernetes Controllers and add opencost cost calculation

[jakepage91]

Is your feature request related to a problem? Please describe.
Using the Kubernetes pods file as an example, add support for Kubernetes controllers

Cost calculation for controllers can be added simply by following the example on line 21 of the pods file example simply passing the controller field

[shubhindia]

@jakepage91 which controller exactly?

[Azanul]

@jakepage91 which controller exactly?

Opencost aggregates costs by k8s primitives. We don't need to pass a specific controller, we want to know how much cost is each controller incurring.

[shubhindia]

There are multiple controllers. Goal is to cover all of them or just the ones which spawn pods?

[Azanul]

There are multiple controllers. Goal is to cover all of them or just the ones which spawn pods?

The high level goal is to calculate cost. Currently we use opencost integration to do so, hence we cover all kinds that opencost covers i.e., deployment, statefulset, daemonset and job.

[asamirr]

We already have deployments implemented so we need to add 3 more files for statefulset, daemonset and job?

[shubhindia]

We already have deployments implemented so we need to add 3 more files for statefulset, daemonset and job?

That's what I was unclear about. Like, only the controllers which spawn pods or other controllers as well like PVC, Ingress etc? Is there any discussion channel available on slack or somewhere? Commenting here is just gonna increase the response time.

[asamirr]

Discord

[jakepage91]

Hey there @shubhindia feel free to joing the discord server, it will for sure reduce the reponse time. So yeah, I wrote up this issue with this section of the OpenCost API docs in mind. As you can see we can choose between controller and controllerKind but we only want to know what cost amount do all controllers incur for now, so I'm guessing that specifying the controller field will be enough