Pro Tips: Use Spinnaker when Kubernetes multi-tenancy is a nightmare
summary
Describes how Adobe used Spinnaker to automate multi-tenant Kubernetes workflows by treating namespaces as individual Spinnaker accounts. Covers a custom pipeline that creates namespaces, onboards accounts, deploys applications, and deletes namespaces for short-lived preview environments, and discusses tackling authorization, fast onboarding, config-file generation and validation, and dynamic account discovery.
AI-written summary · about
related talks
19mSpinnaker Deployments on Kubernetes from a Security Perspective
17mIntroduction to Spinnaker on Kubernetes
45mGetting Started with Spinnaker (part 1)
05mLightning Talk: What Makes a Good Multi-tenant Kubernetes Solution?
27mDeploying Docker Containers with Netflix Spinnaker on Kubernetes and Titus
10mSpinnaker @ Scale for Snap’s Multi Cloud Service Mesh
43mUsing Kubernetes, Spinnaker and Istio to Manage a Multi-cloud Environment
29mNavigating the Multitenancy Maze: Avoiding Kubernetes Antipattern Pitfalls