davidwatkins73
commented
2 years ago Model Would you view this as a new set of entities in Waltz, e.g.:
Cluster :: Node :: Pod :: Contanier :: ....
... the lowest level (service / container / namespace ?) would be associated to apps.
Or would you view this as denormalized entitiy with the cluster,pod etc as attributes ?
Costs Costs can be associated to non-application entities, but currently we record cost information against applications.
We will try and get some views from ourside on how this could be structured as we have little expertise within the team.
Description
We are not only deploying to servers (VM and bare metal), but to Kubernetes Clusters too. Can we enhance Waltz to allow for a further hardware option for being deployed to K8s?
It could be hosted on our own K8s cluster on prem, or to a K8s cluster hosted by a Cloud provider (GCP, AWS etc)
The cost reporting system must aggregate the infrastructure cost categories (CPU, memory, GPU, storage, network and load balancer) in different dimensions that include the following:
Container Pod Cluster Namespace Controller Service Label This level of aggregation is essential when allocating costs across business concepts such as applications, projects, products (SaaS products hosted in a cluster), teams, environments (production versus testing), departments or cost centers. Any business unit to which costs are being allocated should map to a Kubernetes component (such as a namespace)
Resourcing
We would like to add this request to the Waltz team's feature backlog