-
Notifications
You must be signed in to change notification settings - Fork 47
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
Strongly tied to kubernetes? #99
Comments
Yes, the dashboard is not supposed to be tied to a single platform, as Dapr itsself is not ties to a single hosting platform. However I recognize that today there are features that depend on Kubernetes, which should not be the case. Some have been raised here #93. |
If you are looking for another hosting platform to validate a hosting agnostic dashboard- my vote is SF Mesh, although its been a bit quiet on that front lately - I'm hoping one day it will come out of preview but who knows :-) |
Just want to point out that WCF (IMO) lost against REST because it simply tried to be too much for too many configurations.
I wish DAPR was more focused on what it needs to do (.net), before we spend a lot of time on what it could be.
R
From: Mark Fussell <notifications@github.com>
Sent: November 12, 2020 11:30 AM
To: dapr/dashboard <dashboard@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: Re: [dapr/dashboard] Strongly tied to kubernetes? (#99)
Yes, the dashboard is not supposed to be tied to a single platform, as Dapr itsself is not ties to a single hosting platform. However I recognize that today there are features that depend on Kubernetes, which should not be the case. Some have been raised here #93<#93>.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#99 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAEVJVKWYCVYG4LFNMQVV63SPQSRRANCNFSM4TIDZWAQ>.
|
As @msfussell mentioned, Dapr runs on self hosted and Kubernetes only in the meantime. I am closing this issue. Please, reopen if there is any other question related to this discussion. |
From the README
Does this mean the dashboard is concerned that its running either locally or in kubernetes cluster as the only two options, and it won't work hosted anywhere else? (docker compose / swarm, service fabric mesh etc) - I'd be surprised if that were the case but the current statement makes me want to check
The text was updated successfully, but these errors were encountered: