KIND during production

30 views
Skip to first unread message

Ahmet Temiz

unread,
Oct 10, 2022, 2:09:36 AM10/10/22
to kubernetes-sig-testing
I just want know why I have to abandon KIND during production.

regards

Benjamin Elder

unread,
Oct 10, 2022, 2:17:05 AM10/10/22
to Ahmet Temiz, kubernetes-sig-testing
We strongly discourage using KIND in production because it isn't designed for or supported as such.

These priorities drive the design and development focus: https://kind.sigs.k8s.io/docs/contributing/project-scope/

For example:
- There's no supported way to maintain patching and upgrades
- The technology fundamentally lacks things like functioning OOM metrics / various things related to resource restriction at the moment
- As a upstream minimal distro, no additional opinionated security configuration is implemented

KIND clusters are designed to be cheap (relatively), ephemeral, and relatively "standard".
They are not built to span multiple physical machines or as permanent long-lived clusters.

If you'd like to bootstrap a production-grade cluster, please see: 
https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/create-cluster-kubeadm/ (kind uses kubeadm internally, but there's more to using kubeadm directly for serious non-ephemeral clusters)

Which are all part of the Kubernetes project under SIG Cluster Lifecycle.

On Sun, Oct 9, 2022 at 11:09 PM Ahmet Temiz <ahmett...@gmail.com> wrote:
I just want know why I have to abandon KIND during production.

regards

--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-testing" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-te...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-testing/4966a308-dbb7-43ac-8d69-aac8f7a8577cn%40googlegroups.com.

Benjamin Elder

unread,
Oct 10, 2022, 2:19:04 AM10/10/22
to Ahmet Temiz, kubernetes-sig-testing
Note: "using in production" here means serving long-lived production workloads.

KIND is suitable for example:
- developing Kubernetes itself
- Testing application or Kubernetes changes in CI
- Local Kubernetes application development
- bootstrapping Cluster API

Which are all documented use-cases.

Ahmet Temiz

unread,
Oct 10, 2022, 12:04:35 PM10/10/22
to kubernetes-sig-testing
Thank you..
you said " We strongly discourage using KIND in production because it isn't designed for or supported as such."
(pitty!. It seems to be working well and faster with my apps.)

regards

Reply all
Reply to author
Forward
0 new messages