ocm VS helm-charts

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

https://github.com/VictoriaMetrics/helm-charts/commit/128d2a7fa23c717e780655f03df83b03e3d637ac could be the reason

There is also victoriametrics-operator and victoriametrics k8s stack helm chart.

BTW, you can use victoria-metrics-k8s-stack as a drop-in replacement for kube-prometheus-stack.

It is possible to replace kube-prom-stack with VictoriaMetrics stack in every k8s cluster - see https://github.com/VictoriaMetrics/helm-charts/blob/master/charts/victoria-metrics-k8s-stack/README.md

I'm monitoring CPU, memory, disk, network usage etc, the basic stuff available from kubernetes metrics via api. I also have a sidecar pod to send CPU temperature via opentsdb endpoint of Victoria Metrics. I run this helm chart which has operator and db - it can be added to grafana as a Prometheus data source.

There is a k8s stack Helm Chart which can provide the same functionality. Also check VictoriaMetrics Operator docs and our guides .

For metrics there is VictoriaMetrics operator and helm chart, which can be used for monitoring Kubernetes. See this guide.