[Infrastructure as Code (IaC) Pulumi] Use Pulumi kubernetes (K8S) Helm Chart to deploy Grafana Loki Stack
Grafana Loki
Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by Prometheus. It is designed to be very cost effective and easy to operate. It does not index the contents of the logs, but rather a set of labels for each log stream.
This article is about how to use Pulumi, kubernetes (K8S) provider, Helm Chart and TypeScript SDK to deploy Grafana Loki Stack within Kubernetes (K8S).
Loki is a datastore optimized for efficiently holding log data. The efficient indexing of log data distinguishes Loki from other logging systems. Unlike other logging systems, a Loki index is built from labels, leaving the original log message unindexed.
Loki features
-
Efficient memory usage for indexing the logs
By indexing on a set of labels, the index can be significantly smaller than other log aggregation products. Less memory makes it less expensive to operate.
-
Multi-tenancy
Loki allows multiple tenants to utilize a single Loki instance. The data of distinct tenants is completely isolated from other tentants. Multi-tenancy is configured by assigning a tenant ID in the agent.
-
LogQL, Loki’s query language
Users of the Prometheus query language, PromQL, will find LogQL familiar and flexible for generating queries against the logs. The language also facilitates the generation of metrics from log data, a powerful feature that goes well beyond log aggregation.
-
Scalability
Loki works well at small scale. In single process mode, all required microservices run in one process. Single process mode is great for testing Loki, running it locally, or running it at a small scale.
Loki is also designed to scale out for large scale installations. Each of the Loki’s microservice components can be broken out into separate processes, and configuration permits individual scaling of the components.
-
Flexibility
Many agents (clients) have plugin support. This allows a current observability structure to add Loki as their log aggregation tool without needing to switch existing portions of the observability stack.
-
Grafana integration
Loki seamlessly integrates with Grafana, providing a complete observability stack.
Prerequisites
-
Kubernetes (K8s) is an open-source system for automating deployment, scaling, and management of containerized applications.
See Getting started | Kubernetes - https://kubernetes.io/docs/setup/ to leanr more.
-
Pulumi - Modern Infrastructure as Code - https://www.pulumi.com/
Pulumi is a modern infrastructure-as-code platform that allows you to use common programming languages, tools, and frameworks, to provision, update, and manage cloud infrastructure resources.
Install the Pulumi - https://www.pulumi.com/ CLI.
1
2Mac OS X
brew install pulumiSee Download and Install | Pulumi - https://www.pulumi.com/docs/get-started/install/ to learn more about others OS.
-
Node.js - https://nodejs.org/en/
Node.js® is a JavaScript runtime built on Chrome’s V8 JavaScript engine.
Install Node.js - https://nodejs.org/en/ CLI.
1
2Mac OS X
brew install nodeSee Node.js - https://nodejs.org/en/ to learn more about others OS.
Usage
Pulumi New
Create the workspace directory.
1 | mkdir -p col-example-pulumi-typescript-loki-stack |
Pulumi login into local file system.
1 | pulumi login file://. |
Pulumi new a project with kubernetes-typescript SDK.
1 | pulumi new kubernetes-typescript |
The above command will create some files within the current directory.
1 | tree . -L 1 |
Install js-yaml
package to load and parse yaml file.
1 | npm i js-yaml |
Pulumi Configuration
Configure Kubernetes
By default, Pulumi will look for a kubeconfig file in the following locations, just like kubectl:
-
The environment variable:
$KUBECONFIG
, -
Or in current user’s default kubeconfig directory:
~/.kube/config
If the kubeconfig file is not in either of these locations, Pulumi will not find it, and it will fail to authenticate against the cluster. Set one of these locations to a valid kubeconfig file, if you have not done so already.
Configure Values.yaml
Edit values.yaml and replace content within {{ }}
.
You should have a exist StorageClass
in order to persistent data for Granfa and Granfa Loki.
1 | # loki/values.yaml at master · grafana/loki |
See and modify main.ts file.
1 | // main.ts |
Pulumi Up
Run pulumi up to create the namespace and pods.
1 | pulumi up |
See pods about loki-stack.
1 | kubectl get pods -n loki-stack |
Then, you can visite Grafana Loki with https://{{ .Values.host }}
.
FAQs
no matches for kind “ClusterRole”, “ClusterRoleBinding”, “Role” in version “rbac.authorization.k8s.io/v1beta1” since Kubernets (K8S) v1.22
The rbac.authorization.k8s.io/v1beta1
API version of ClusterRole
, ClusterRoleBinding
, Role
, and RoleBinding
is no longer served as of v1.22.
-
Migrate manifests and API clients to use the
rbac.authorization.k8s.io/v1
API version, available since v1.8. -
All existing persisted objects are accessible via the new APIs
-
No notable changes
no matches for kind “Ingress” in version “networking.k8s.io/v1beta1” since Kubernets (K8S) v1.22
1 | Verify that any required CRDs have been created: no matches for kind "Ingress" in version "networking.k8s.io/v1beta1" |
The extensions/v1beta1
and networking.k8s.io/v1beta1
API versions of Ingress is no longer served as of v1.22.
-
Migrate manifests and API clients to use the
networking.k8s.io/v1
API version, available since v1.19. -
All existing persisted objects are accessible via the new API
Notable changes:
- spec.backend is renamed to spec.defaultBackend - The backend serviceName field is renamed to service.name - Numeric backend servicePort fields are renamed to service.port.number - String backend servicePort fields are renamed to service.port.name - pathType is now required for each specified path. Options are Prefix, Exact, and ImplementationSpecific. To match the undefined v1beta1 behavior, use ImplementationSpecific.
See Deprecated API Migration Guide | Kubernetes - https://kubernetes.io/docs/reference/using-api/deprecation-guide/ to learn more.
First, create new Ingress with networking.k8s.io/v1
API version.
1 | # Ingress.loki-stack-grafana.yaml |
See Ingress | Kubernetes - https://kubernetes.io/docs/concepts/services-networking/ingress/ to leanr more.
Then, run kubectl apply
command.
1 | kubectl apply -f Ingress.loki-stack.yaml Ingress.loki-stack-grafana.yaml |
Now, you can visite Grafana Loki with https://{{ .Values.host }}
.
no matches for kind “Ingress” in version “extensions/v1beta1” since Kubernetes (K8S) v1.22
1 | Verify that any required CRDs have been created: no matches for kind "Ingress" in version "extensions/v1beta1" |
Same as above no matches for kind "Ingress" in version "networking.k8s.io/v1beta1" since Kubernets (K8S) v1.22
.
Pulumi Destroy
Destroy all resources created by Pulumi.
1 | pulumi destroy |
References
[1] Grafana Loki | Grafana Labs - https://grafana.com/oss/loki/
[2] grafana/loki: Like Prometheus, but for logs. - https://github.com/grafana/loki
[3] Helm | Grafana Labs - https://grafana.com/docs/loki/latest/installation/helm/
[5] loki-stack 2.4.1 · grafana/grafana - https://artifacthub.io/packages/helm/grafana/loki-stack
[6] Kubernetes Getting Started | Pulumi - https://www.pulumi.com/docs/get-started/kubernetes/
[7] Pulumi - Modern Infrastructure as Code - https://www.pulumi.com/
[8] Kubernetes - https://kubernetes.io/
[9] TypeScript: Typed JavaScript at Any Scale. - https://www.typescriptlang.org/
[11] Ingress | Kubernetes - https://kubernetes.io/docs/concepts/services-networking/ingress/