ocm VS gardener

Open Cluster Management (OCM) was accepted to the Cloud Native Computing Foundation (CNCF) in late 2021 and is currently at the Sandbox project maturity level. OCM is a community-driven project focused on multicluster and multicloud scenarios for Kubernetes applications. This article shows how to bootstrap Open Cluster Management and handle work distribution using ManifestWork. We also discuss several ways to select clusters for various tasks using the ManagedClusterSet and Placement resources.

It seems that open-cluster-management.io is a great tool for enforcing configurations and policies in a vendor-agnostic manner. When looking at all possible modifications supported by it, this tool does not yet use Daemonsets for customizing the core Kubernetes framework itself to the needs of the applications deployed on it.

You can use https://open-cluster-management.io/ With the multi cluster observability https://github.com/stolostron/multicluster-observability-operator This would be perfect for multi-cluster monitoring

There's a number of options here. Like the other commenter mentioned, RHACM is a great choice if you already have an OCP cluster - ie a tools cluster, multi-cluster deployments, etc. It is paid, but there is a 60 day free trial. Also, like other RH products, it is based on an OSS upstream project, in this case Open Cluster Management.

Someone already said ClusterAPI. It is great to build the clusters and manage their lifecycle. To manage very thing until the cluster is retired check out https://open-cluster-management.io.

It is "publicly" available in that all of the code is there so that you can build and use it. Some of that is pre-build via the Open Cluster Management project, but some is not.

Open Cluster Management (the backbone of Advanced Cluster Management) might help you deploy applications and such to multiple clusters!

There is this: https://github.com/open-cluster-management-io/OCM, which is the upstream project for Red Hat Advanced Cluster Management for Kubernetes

Now, if you want to dig further on how cloud providers operate, like I said, most are actually using Kubernetes to automate the client control plane management. There is a cloud-neutral project for this out there called Gardener, they have a few architecture documents which explain the concept a bit further. In their garden metaphor, the seed cluster hosts the client control planes, and the shoot clusters are the client clusters (which are only made of worker nodes, no control-plane node). Another more specialized implementation is Kubernikus for OpenStack.

Gardener: https://github.com/gardener/gardener RH HyperShift: https://github.com/openshift/hypershift

Gardener does exactly that. One global cluster manages smaller per-region/cloud provider management clusters and those will contain the control planes of your workload clusters. This way you can have like 10 000 clusters and not deal with multi-tenant issues. One workload = 1 cluster.

We had cluster of cluster style management managing 100s of cluster. Check out https://github.com/gardener/gardener for an inspiration

How does this compare against simply using Gardener [0]?

[0] https://github.com/gardener/gardener