Kure – Kubernetes pod-failure monitor with LLM-assisted diagnosis

igor-koricanac1 pts0 comments

Installation | Kure Monitor<br>Skip to content

Installation

This guide covers how to install Kure Monitor on your Kubernetes cluster. Kure ships as a Helm chart; raw k8s/ manifests are no longer maintained.

Prerequisites<br>Section titled “Prerequisites”

Kubernetes cluster (1.20+)

kubectl configured to access your cluster

Helm 3.x

Cluster admin permissions

Helm install<br>Section titled “Helm install”

Add the repository<br>Section titled “Add the repository”

Terminal windowhelm repo add kure-monitor https://nan0c0de.github.io/kure-monitor/

helm repo update

Basic install<br>Section titled “Basic install”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)"

Install with custom values<br>Section titled “Install with custom values”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)" \

--set frontend.service.type=LoadBalancer

Install from a local checkout<br>Section titled “Install from a local checkout”

Terminal windowgit clone https://github.com/Nan0C0de/kure-monitor.git

cd kure-monitor

helm install kure-monitor ./helm \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)"

Post-install<br>Section titled “Post-install”

1. Verify<br>Section titled “1. Verify”

Terminal windowkubectl get pods -n kure-system

Expected:

NAME READY STATUS RESTARTS AGE

kure-monitor-agent-xxxxx 1/1 Running 0 1m

kure-monitor-backend-xxxxx 1/1 Running 0 1m

kure-monitor-frontend-xxxxx 1/1 Running 0 1m

kure-monitor-security-scanner-xxxxx 1/1 Running 0 1m

postgresql-xxxxx 1/1 Running 0 1m

2. Access the dashboard<br>Section titled “2. Access the dashboard”

Port-forward (development):

Terminal windowkubectl port-forward svc/kure-monitor-frontend 8080:8080 -n kure-system

# http://localhost:8080

NodePort:

Terminal windowkubectl get svc kure-monitor-frontend -n kure-system

# http://:30080

LoadBalancer:

Terminal windowhelm upgrade kure-monitor kure-monitor/kure \

--set frontend.service.type=LoadBalancer \

-n kure-system

Ingress:

Terminal windowhelm upgrade kure-monitor kure-monitor/kure \

--set ingress.enabled=true \

--set ingress.hosts[0].host=kure.example.com \

-n kure-system

3. Create the initial admin<br>Section titled “3. Create the initial admin”

On first visit, the dashboard prompts you to create the initial admin account (username + password). After signing in, go to Admin → Users to invite further users with read, write, or admin roles.

Authentication is always on in 2.3+ and is wired up automatically by the Helm chart — there is nothing to configure at install time. The legacy auth.apiKey single-key model was removed in 2.3.0. See Authentication and the 2.2 → 2.3 migration guide for details.

4. Configure an LLM provider<br>Section titled “4. Configure an LLM provider”

Open the dashboard

Go to Admin Panel → AI Configuration

Pick a provider (OpenAI, Anthropic, Groq, Gemini, GitHub Copilot, or Ollama)

Enter your API key

Pick a model

Click Test Connection , then Save

See LLM Providers for the full list of supported models.

Upgrading<br>Section titled “Upgrading”

Terminal windowhelm repo update

helm upgrade kure-monitor kure-monitor/kure -n kure-system

Uninstalling<br>Section titled “Uninstalling”

Terminal windowhelm uninstall kure-monitor -n kure-system

kubectl delete namespace kure-system # removes all data

Cloud-specific notes<br>Section titled “Cloud-specific notes”

Amazon EKS<br>Section titled “Amazon EKS”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)" \

--set frontend.service.type=LoadBalancer \

--set frontend.service.annotations."service\.beta\.kubernetes\.io/aws-load-balancer-type"=nlb

Requires the AWS Load Balancer Controller for LoadBalancer services.

Google GKE<br>Section titled “Google GKE”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)" \

--set frontend.service.type=LoadBalancer

Azure AKS<br>Section titled “Azure AKS”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)" \

--set frontend.service.type=LoadBalancer

Minikube<br>Section titled “Minikube”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)"

minikube service kure-monitor-frontend -n kure-system

Kind<br>Section titled “Kind”

Terminal windowhelm install kure-monitor kure-monitor/kure \

--namespace kure-system \

--create-namespace \

--set postgresql.password="$(openssl rand -hex 24)"

kubectl port-forward svc/kure-monitor-frontend 8080:8080 -n...

kure monitor install section titled namespace

Related Articles