Draft: allow creating an OpenShift route

[kastl-ars]

This is not meant as a PR ready to merge. I just wanted to start a discussion, if the functionality to create an OpenShift route via the helm chart would be something worth adding.

I know the chart can create an ingress, but if you want to put OpenCost behind a oauth-proxy, you need to put the route name into an annotation on the serviceAccount. And if the route is being created from an ingress automatically, its name contains a random hash...

[AjayTripathy]

@kastl-ars I'm supportive of this idea! @mittal-ishaan you've been working in this area, do you have any thoughts?

[mittal-ishaan]

I completely agree with @kastl-ars
In addition, I’d like to propose a discussion around introducing an openshift block in the Helm chart to have all OpenShift-specific configurations, such as Routes and in-cluster Prometheus integrations. This change would:

• Ensure OpenShift-specific features are enabled only in OpenShift environments.
• Address specific requirements like volume mounts for OpenShift, avoiding workarounds such as those mentioned in opencost-ui issue #4. This could either be solved or a workaround be included as a default in helm chart itself.

Thoughts?

[kastl-ars]

I think the addition of an openshift block, that globally triggers e.g. the proper setting of the securityContext, would be nice. But I would propose to keep things separate, i.e. let this PR only be about adding a route.

Otherwise I fear this becomes to big to properly test and review...

[mittal-ishaan]

yes, agree we can do it in a separate PR. Addition of openshift Route in the helm chart looks good to me.

[kastl-ars]

Does anyone have better documentation on OpenShift routes than the incomplete and "going into obscure corner cases too fast" documentation here. Especially the exact details on the tls section are hard to find...