Multi-cluster topologies are a key part of Kubernetes. Organisations gain many benefits using multiple clusters, such as increased scale, bespoke APIs, blast radius reduction and more. However, multi-cluster deployments also increase complexity.

With multiple clusters comes increased building and maintenance complexity for the platform team. Answers to questions like which cluster to install certain tools into, how to provision newly created clusters in a standard way, and whether to provide ephemeral cluster environments, are becoming more important. These answers often come with a whole host of technologies as baggage.

This workshop will explore how to use a higher level framework to encapsulate your platform offerings. And with these now packaged offerings, you can automate their availability according to business requirements across both existing and future clusters to build a powerful platform that supports engineering productivity and business requirements.

A fallacy is a kind of error in reasoning that should not be persuasive, but often are. Fallacies may be created unintentionally, or they may be created intentionally in order to deceive other people. The vast majority of the commonly identified fallacies involve arguments, although some involve explanations, or definitions, or other products of reasoning. Sometimes the term "fallacy" is used even more broadly to indicate any false belief or cause of a false belief.

In this talk, we will explore the common fallacies people believe in regards to platform building, both as supporters and opponents of it. We will give them names, analyse their flaws, and how they are often used in arguments. The goal is to give you the tools you need to spot and rebuke them next time they appear in your team discussions.

After this talk, you will:
* Learn about common fallacies around platform building
* Learn how to spot a fallacy in a team discussion
* Understand how to counter-argument a fallacy