# kind Published articles for kind. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## LoadBalancer Services using Kubernetes in Docker (kind) DevFeed: [LoadBalancer Services using Kubernetes in Docker (kind)]() Original publisher: [Read original article]() Author: Owain Williams Published: 2022-09-20T20:08:29Z Content type: tutorial Language: en Sources: [Groupon Engineering -- Medium]() Topics: [Kubernetes](), [Docker](), [Orchestration](), [container](), [Development]() Tags: [container](), [development](), [docker](), [ingress](), [kind](), [kubernetes](), [load-balancer](), [orchestration]() ### AI overview This tutorial introduces Kubernetes and compares local options for experimenting with it, including Docker's single-node cluster, minikube, and kind. It explains that kind runs cluster nodes in containers and supports multi-node clusters, but the supplied text ends during cluster creation. ### Source excerpt Kubernetes is a very popular open-source container orchestration system for deploying, scaling, and updating your software, as well as automatically recovering from failures. If your code can be packaged into a container, e.g. via Docker, then it can run on Kubernetes, or k8s for short (which is sometimes pronounced 'kates' and refers to the 8 letters between the first and last letter). You can read more about it on the Kubernetes Documentation page. You can run a Kubernetes cluster in your own data centre as well as on many of the popular cloud providers, for example there's the Amazon Elastic Kubernetes Service (EKS), the Azure Kubernetes Service (AKS), and the Google Kubernetes Engine (GKE) to name a few. You can also create clusters that span your data centre and a cloud provider or even span multiple cloud providers. Here at Groupon, we have several Kubernetes clusters around the world hosted on both EKS and GKE. This is great for production, or even as a staging cluster, or shared development environment. But what if you just want to try it out and see what all the hype is about before you spend money on a new cluster? The good news is there are several options, if you've installed Docker you can enable a single-node Kubernetes cluster simply by ticking the option in the Docker settings. However, you will be tied to the version of Kubernetes that ships with your version of Docker. Another option is minikube which allows you to run specific versions of Kubernetes, or even multiple clusters with different versions. However, you'll still only be able to run single-node clusters. A single-node cluster is probably fine, and could well be all you ever need. But you won't be able to experiment with pods running on different nodes, and the various like-live scenarios that enable, for example using hostPath volumes with different files on each node. Before you fire up a load of VMs and try installing Kubernetes The Hard Way there is one more option, kind, which stands ## A new App Engine datastore API DevFeed: [A new App Engine datastore API]() Original publisher: [Read original article]() Author: Guido van Rossum (noreply@blogger.com) Published: 2011-01-07T20:20:00Z Content type: release Language: en Sources: [Guido van Rossum]() Topics: [Python](), [API](), [Databases](), [Open Source](), [generators](), [Coroutines]() Tags: [api](), [appengine](), [classes](), [coroutines](), [design](), [generators](), [kind](), [open-source](), [python]() ### AI overview Guido van Rossum introduces Datastore Plus, a preliminary redesign of the Python datastore API for App Engine users. The proposal includes cleaner Key, Model, Property, and Query implementations and a high-level asynchronous API using Python generators as coroutines. The implementation is available as an open-source project for review, with feedback requested on its documentation, implementation, and API design. ### Source excerpt This post is primarily intended for App Engine users (and of those, only Python users :-). Over the past months I've been working on a new design for the Python datastore API, under the code name Datastore Plus. The new design is very ambitious, and changes a lot of things: New, cleaner implementations of Key, Model, Property and Query classes High-level asynchronous API using Python generators as coroutines (PEP 342) The design is meant to eventually replace the existing db package in the App Engine runtime library, but for now, it is just an open source project which you have to download and copy into your application. I am not at all finished with this design, but I believe in listening to users, so I am making a preliminary version of the new API available for review. Please send me your thoughts, either in this blog, or via private mail to guido (at) google.com. Note that the implementation works, but I cannot guarantee that it won't change. Documentation is here: http://goo.gl/D6Onw The project to check out is here: http://goo.gl/GapXI You must use Mercurial to check out the project, but it's fine to check it out anonymously -- I don't require anybody to log in to look or comment. (If using Mercurial is too much of a burden, there's also a zipfile on the site, but I don't plan to update it frequently.) I'm interested in receiving any kind of feedback at all. It would help me if you could clarify whether your feedback is about an issue with the documentation, an issue with the implementation, or an issue with the API design -- though I realize you can't always tell the difference. :-) (You can also comment on the thread in the google-appengine-python group here: https://groups.google.com/group/google-appengine-python/browse_thread/thread/454cb81d49e759f2.)