-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Who is supporting OAM in their offering? #295
Comments
Yeah, Alibaba Enterprise Distributed Application Service has already supported OAM. Also Crossplane has plan to support. As far as I know, Microsoft also has some Enterprise Service to support OAM, right? I think we could list them together. |
Adding @suhuruli but I don't think Microsoft has it in their offering (yet), right? I'm more than happy to send a PR with this, just need to figure out the best location for this. How about oam.dev as part of the |
rainbond is also going to support OAM, it's written in Chinese now goodrain/rainbond#616. |
Thoughts on the rough idea @wonderflow? |
Yeah, I think it's good. \cc @resouer @hongchaodeng |
Great, I'll open a PR next week then and include Crossplane & Rainbond as "coming soon". Any other implementations that we are missing? Adding a couple of MSFT folks as well @suhuruli @vturecek @technosophos |
We also have a ROS runtime of OAM, we're planning to create a repo in |
PR is open, all feedback is welcome! |
This is live on https://oam.dev/#implementations |
A question I get a lot is:
As far as I know, this is not true since Alibaba Enterprise Distributed Application Service this as a managed service as well or am I wrong @xiang90 @wonderflow? Maybe other vendors support this as well.
It would be good if we could provide a list for users to see where they can use it which helps them decide if they should adopt the Open Application Model or not. Today, it feels like this is holding people back from adapting "since it only supports Kubernetes".
The FAQ (#239) or listing on oam.dev feels like good places as it should be pretty "in your face".
The text was updated successfully, but these errors were encountered: