Cloud Foundry Day Europe 2024

Estimating and understanding cloud costs is difficult exercise. It gets even more complex when attempting to do this with Kubernetes at scale. What really obfuscates it the most is when you install an abstraction that is meant to manage build, deployment, scaling, and all other functions. OpenCost lifts the veil on Kubernetes spending. This open-source project delivers real-time cost allocation, giving you a detailed breakdown from entire deployments down to individual containers. It integrates seamlessly with major cloud providers (AWS, Azure, GCP) and even supports on-premises clusters, ensuring dynamic asset pricing for all Kubernetes environments. When applied to Korifi, it tells us many things. In this talk, I intend to explore what it costs to operate the tool on Kubernetes clusters. Can we find out what a build costs? Can we ascertain the cost of scaling an instance? Come to the talk to find out!

Come listen to how our community migrated from using Terraform to using OpenTofu. In this talk, I will showcase CloudServiceBroker, a project that aims to make it easier for services to be enabled when using CF. The Services MAnagement working group recently decided to switch from using Terraform to using OpenTofu for all their needs. OpenTofu replaced Terraform in the CSB starting with version 1.0.0. This talk explores the technology, process, and the human element in the whole process.

Currently, the Cloud Foundry routing stack does not support the configuration of features for a specific route. A case in point is the load balancing algorithm between Gorouters and backends. This algorithm is defined globally and is utilized generically to distribute requests among available backends for a given route. The ability to define the load balancing algorithm on a per-route basis could help in optimizing the use of application instances, based on the workloads on the application side. In this talk Tamara and Max, on behalf of the SAP BTP CF Routing team, present several scenarios for which a more flexible approach of per-route functionalities can provide benefits. They are going to highlight a proposed solution that keeps the implementation overhead as simple as possible. Furthermore, they will talk about the current implementation state and challenges we have encountered. This talk is intended to raise some further discussions and ideas that could be integrated as a per-route feature.