[P1BIGROCKS-2421](https://jira.il2.dso.mil/browse/P1BIGROCKS-2421) # Summary Currently BigBang assumes that the `v1beta1.metrics.k8s.io` API Service Endpoint (and a `kube-metrics` deployment with it) will be available by default in clusters using BigBang. This assumption stems from the endpoint being provided as part of Rancher and K3s (among others) by default. However, other k8s distributions such as Konvoy do not provide this endpoint or a `kube-metrics` deployment by default. Without this endpoint, Horizontal Pod Autoscalers, `k top` commands, and other processes that rely on this endpoint for gathering metrics about the cluster will fail. This epic should provide resources to BigBang end users to inform them of the assumptions made by a default BigBang deployment (where no `v1beta1.metrics.k8s.io` endpoint is configured for them) as well as provide an alternative means for allowing BigBang users to deploy their own metric endpoint in the event their k8s distribution does not. Acceptance Criteria: - [x] Documentation is provided to inform BB users of the lack of metrics endpoint provided by a default deployment of BigBang (we shouldn't assume they want one by default) - [x] A package is added to provide a metrics service and endpoint that can be deployed optionally as part of BigBang.