spec
spec copied to clipboard
oam-dev
Open Application Model (OAM).
如果我的理解没有偏差的话，目前 OAM 是通过 [Traits](https://github.com/oam-dev/spec/blob/master/6.traits.md) 来定义应用就绪的约定条件。 ## Background information 众所周知，以当前 kubernetes 作为大环境，应用以 docker container 形式运行在 ☁️ 之上。而目前就绪探测（readinessProbe）定义的三种形式在我看来都有问题。 1. tcpSocket 和 httpGet 都过于简单粗暴； 1. exec 比较hack，普遍性不强，而且还得把 bash ”藏“在镜像里面； ## What‘s healthy web...
As per discussion of the "OAM Resource Composition Proposal" on 2020-01-28 community meeting, since workload such as Serverless Function and VM are supported via Extended WorkloadType, by not enforcing schema...
It happens that a Dev may have some opinion about the Traits for this application. More generally, the Dev (who understand how the app is developed in code level) may...
With the introduction of extended workload types, we may need to have a way to pipe the output of components into parameters of other components.Consider the following deployment: - Component...
First of all, OAM is not an orchestration system so handling dependency is not a concern of OAM spec. The intention of this issue is raising a need for another...
Most of our users told us that we need to make `container.image` of ComponentSchematic to be configurable. The case is that once the component has been created, only image tag...
Does the OAM spec require runtimes support ONLY the fields defined by the spec, or may they choose to support additional fields? Currently the OAM spec does not touch on...
Currently OAM defines the schema for a Container that is _very_ similar to, but not exactly the same as the Kubernetes Container. The OAM spec probably cannot use the exact...
### Issue What is the use of workload name in Component? There is only one workload per Component, so what is the reason for metadata AND spec? Name seems useless...
