Why does Kubernetes need a unified application model? It would be the final piece needed to run a seamless deployment model. By Joab Jackson.
With a solid application model in place, a developer could finally build a cloud native application on a laptop, and have it work seamlessly — with no modifications — in a production environment, Prasek said. Without a solid app model, the deployment workflow gets too quickly mired in complexities, slowing things down.
A model connecting the developer to production, asserted Phil Prasek, a principal product manager at cloud services provider Upbound, in a breakout session at the KubeCon + CloudNativeCon Europe.
Source: https://thenewstack.io/oam-the-kubernetes-application-model-bridging-development-and-deployment/
The mission of the newly-formed Cloud Native Computing Foundation‘s sig-app-delivery Special Interest Group is to provide a standard way of defining the operational requirements for applications running across Kubernetes.
The Open Application Model (OAM), from Microsoft and Alibaba, is one such model. The goals of OAM are twofold, according to OAM contributor Ryan Zhang:
- Provide a standard application context for any microservice platform
- Define a team-centric model that supports a clear separation of concerns between developers and operators
Plenty of resources and explanations in this article together with link to the talk about “Towards a Standardized Application Definition Model for Kubernetes”. Great job!
[Read More]