Loki Coordinator K8S
- Canonical Observability
Channel | Revision | Published | Runs on |
---|---|---|---|
latest/edge | 15 | 03 Dec 2024 | |
latest/edge | 1 | 12 Aug 2024 |
juju deploy loki-coordinator-k8s --channel edge
Deploy Kubernetes operators easily with Juju, the Universal Operator Lifecycle Manager. Need a Kubernetes cluster? Install MicroK8s to create a full CNCF-certified Kubernetes system in under 60 seconds.
Platform:
Charmed Loki Coordinator
loki-coordinator-k8s
is a workloadless charm that coordinates the operations of loki-worker
charms and routes traffic to them.
It is an essential part of COS HA.
This Charmed Operator handles deployment, scaling, configuration, and Day 2 operations specific to Loki.
This operator drives the Loki worker applications, and it can be composed with other operators to deliver a complex application or service.
Loki-coordinator’s primary task is to ensure that a cluster of Loki worker nodes is consistent (i.e. all required roles are assigned to a certain number of units). Its secondary function is to provide a unified configuration point for the whole cluster. Finally, it deploys and operates nginx to route traffic to the related workers.
This charm on its own does not deploy or operate Loki; the loki
bundle deploys a loki-coordinator
instance and a loki-worker
instance and integrates them. Only then, you will have a functional Loki deployment.
This charm is:
- part of the COS HA bundle
- intended to be used together with
alertmanager-k8s
In this documentation
Tutorial Get started - a hands-on introduction for new users deploying the charmed operator. |
How-to guides Step-by-step guides covering key operations and common tasks |
Explanation Concepts - discussion and clarification of key topics |
Reference Technical information - specifications, APIs, architecture |
Project and community
Charmed Loki is part of the Canonical Observability Stack. It’s an open source project that warmly welcomes community projects, contributions, suggestions, fixes and constructive feedback.
Thinking about using the Canonical Observability Stack for your next project? Get in touch: