Portfolio ↗

Platform Tenancy

Isolating teams sharing a cluster, account or pipeline fleet, and where isolation must be hard.

6Questions
11Flashcards
4Terms
Drill this topic All of Platform Engineering & Developer Experience
Questions

6 to work through

  1. advanced

    A platform serves internal teams with very different scale and criticality. Should they share infrastructure?

    1 min answer
  2. advanced

    An internal platform hosts workloads from many teams. What isolation model should it use, and how are noisy neighbours handled?

    2 min answer
  3. advanced

    An internal platform serves many product teams with very different scale and criticality. How should isolation between them be designed?

    2 min answer
  4. advanced

    On 11 December 2024 OpenAI deployed a new telemetry service into its Kubernetes clusters. Its configuration caused every node to perform Kubernetes API operations whose cost scaled with the size of the cluster; API servers saturated and DNS-based service discovery failed across most large clusters, with services unavailable from 15:16 to 19:38 PST. The change had been tested in staging. What structurally failed, what could staging not test, and where would copying their response be a mistake?

    3 min answer
  5. advanced

    On a shared cluster serving twelve teams, one team's new operator creates a custom resource per user session, reaching about 50,000 objects in a day. Other teams start seeing slow deploys and intermittent API timeouts. What is happening inside the cluster?

    3 min answer
  6. advanced Multiple choice

    Twelve teams, forty services. One shared Kubernetes cluster or a cluster per team? Justify.

    1 min answer
Terminology

4 terms in this topic

concept

Cluster Multi-Tenancy

Multiple teams or workloads sharing one cluster, isolated by namespaces, quotas and policy rather than by separate infrastructure.

 pattern

Namespace Tenancy

Isolating teams within a shared cluster by namespace plus quota plus network policy, and being explicit about what that does not isolate.

 concept

Noisy Neighbour

One workload degrading others by consuming a shared resource - and specifically the resources nobody set limits on, such as control-plane capacity, n…

 practice

Object Count Quota

A per-tenant limit on how many control-plane objects a team may create, which is the control that prevents one team's design choice from exhausting t…
Platform Engineering & Developer Experience

Neighbouring topics

Platform Engineering

General material on internal platforms as products with users, adoption and lifecycles.

4 quiz 8 cards 3 terms

Internal Developer Platform

The assembled surface teams actually touch, and what belongs behind it.

4 quiz 7 cards 4 terms

Paved Road & Golden Path

A supported default route that is easier than the alternatives rather than mandatory.

3 quiz 9 cards 3 terms

Self-Service Provisioning

Teams getting infrastructure without a ticket, and the guardrails that make that safe.

6 quiz 7 cards 4 terms

Service Templates

Scaffolding new services with observability, CI and security already wired in.

4 quiz 8 cards 4 terms

Platform APIs

Treating the platform's own interfaces as contracts with consumers and compatibility rules.

4 quiz 8 cards 3 terms

Cluster Architecture

How many clusters, split by what, and the blast radius each split buys.

6 quiz 13 cards 4 terms

Service Mesh Operations

What a mesh genuinely solves, its failure modes, and the cost of running one.

5 quiz 7 cards 3 terms

Container Image Strategy

Base images, layer hygiene, rebuild cadence, and patching a fleet of images.

4 quiz 10 cards 4 terms

Developer Environments

Local, remote and ephemeral environments, and the fidelity each can honestly claim.

4 quiz 5 cards 3 terms

Inner Loop & Outer Loop

Where an engineer's time actually goes, and which loop a platform investment shortens.

5 quiz 9 cards 3 terms

Abstraction Level Choice

How much to hide, and the leak that turns a helpful abstraction into a trap.

4 quiz 9 cards 5 terms

Platform SLOs

Committing to reliability for internal consumers who cannot choose another provider.

5 quiz 9 cards 3 terms

Platform Adoption

Migrating existing teams onto a platform without a mandate, and reading the adoption curve.

5 quiz 7 cards 5 terms

Platform Funding

Central cost, showback, chargeback, and justifying a team that ships no customer feature.

6 quiz 8 cards 3 terms

Platform API Deprecation

Removing something dozens of internal teams depend on, on a timeline that holds.

5 quiz 11 cards 3 terms

Guardrails vs Gates

Preventing a class of mistake automatically versus stopping to ask a human.

5 quiz 11 cards 2 terms

Platform Telemetry

Instrumenting the platform itself: usage, friction, and where teams leave the paved road.

4 quiz 9 cards 4 terms

Platform Team Topologies

Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.

3 quiz 10 cards 3 terms