KEP-706keps/sig-apps/706-portable-service-definitions
Portable Service Definitions
The goal of this feature is to enable an application to be deployed into multiple environments while relying on external services that are not part of the application and using the same objects in all environments. That includes service instances that may or may not be managed by Kubernetes. For example, take a WordPress application that relies on MySQL. If… Full summary
The goal of this feature is to enable an application to be deployed into multiple environments while relying on external services that are not part of the application and using the same objects in all environments. That includes service instances that may or may not be managed by Kubernetes. For example, take a WordPress application that relies on MySQL. If the application is running in GKE or AKS it may leverage a Google or Azure MySQL as a Service. If it is running in Minikube or in a bare metal cluster it may use MySQL managed by the Kubernetes cluster. In all of these cases, the same resource is declared asking for the service (e.g., MySQL) and the credentials to use the service are returned in a common manner (e.g., a secret with the same type and schema). This enables portability from one environment to another because working with services in all environments leverages the same Kubernetes objects with the same schemas.
Facts
- Authors
- @mattfarina
- Approvers
- @prydonius@mattfarina@kow3ns
- PRR approvers
- none
- Tracking issue
- #706(opens GitHub in a new tab) closedcompletedclosed 2020-05-08 18:03 UTCsig/apps
- Milestones
- none
- Participating SIGs
- none
- Feature gates
- none
- Created / last updated
- 2018-11-13 / 2018-11-19