Lei Zhang (Harry)
Lei Zhang (Harry)
Thanks! `experimental.core.oam.dev/v1alpha2` LGTM We will need to add a section in OAM k8s runtime doc to claim what does this mean.
@saad-ali That's great. Has the issue been sent out?
@crazykev pay attention to this issue for ocid work please
xref: https://github.com/clux/kube-rs/issues/9
Knative and KEDA should be put at high priority as well. Aka, Rudr Serverless :-)
@omkensey Hi Joe, the OAM spec has been released to v1alpha2 which is slightly different, for example, ComponentSchematic is gone :-) Please check [this slides](https://speakerdeck.com/resouer/whats-new-in-oam-v1alpha2-spec) for a diff. The recommend...
In general, traffic mgmt related apps like `BookInfo` should be able to be modeled easily with OAM. The mapping would be: - _Component_ - Deployment - _Trait_ - Service/Ingress **per**...
My personal feeling is, for an implementation (e.g. Rudr), its type is "subset" of OAM spec type is fine as long as it will not bring fragmentation to OAM.
Maybe change the spec to optional?
/cc @wonderflow