You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of building/running all the Quickstarts locally, we should also add container images and deployment files so they can be run quickly in Kubernetes (either locally or in the cloud). Creating images and running apps on Kubernetes is still a big learning curve for many developers so lets try to make it easier for them to run Dapr Quickstarts on K8s.
I suggest we start with one API (PubSub) for each of the languages in QS Pubsub to see if this works. When we have this initial set of images, other contributors can help out to build images for the other APIs.
The text was updated successfully, but these errors were encountered:
Hey @marcduiker yes I'm very interested in this idea. I feel it can help productivity a lot. In fact, having Kubernetes flavors of quickstarts is probably the most interesting goal here; and having container images is a side implementation detail.
The challenge is docker and podman have added notable challenges and instabilities to our matrix testing, and I spend a lot of time wrestling with that already. So I'd want to make sure we maintain or improve stability in process, and not make life worse. If we can't test, we can't scale, no matter how productive it is.
Describe the feature
Instead of building/running all the Quickstarts locally, we should also add container images and deployment files so they can be run quickly in Kubernetes (either locally or in the cloud). Creating images and running apps on Kubernetes is still a big learning curve for many developers so lets try to make it easier for them to run Dapr Quickstarts on K8s.
I suggest we start with one API (PubSub) for each of the languages in QS Pubsub to see if this works. When we have this initial set of images, other contributors can help out to build images for the other APIs.
The text was updated successfully, but these errors were encountered: