Wikimedia Release Engineering Team/Seakeeper proposal/Kubernetes vendor selection

= Kubernetes vendor selection =

Overview
Kubernetes vendor criteria will be derived from past work on Future CI requirements and the  Seakeeper proposal. Requirements herein defined are scoped such that they cover only the products, services and relationship WMF Release Engineering is seeking to establish with a Kubernetes PaaS provider for the purpose of rolling out and maintaining an Argo based CI system. These requirements must bolster those of the greater CI system—and should directly reference them when relevant—but may also be informed by considerations outside the precise purview of CI.

Discussion between primary participating stakeholders should drive the creation of these requirements and should be kept to the discussion page of this article as much as possible.

Categories
Requirements will be broken down into these distinct categories:


 * Functional: Requirement speaks to the operational behavior of the provided k8s PaaS and the material needs of admins and users.
 * Non-functional: Requirement speaks to the qualities of the provided k8s PaaS and our needs around availability, usability, scalability, performance, maintainability, and more. Some NFRs may be attached to one or more specific service level objectives (SLOs).
 * Organizational: Requirement speaks to the vendor organization itself, its history and capacity to deliver, or its potential relationship with WMF with regard to culture and values.