Official Helm charts for deploying TAINUX Doctor AI on Kubernetes, OKD and Red Hat OpenShift. Add the repository, install with a single command and start diagnosing your cluster in minutes.
The TAINUX Helm repository provides charts designed for standard Kubernetes clusters, OKD and Red Hat OpenShift environments. Charts are versioned, signed and follow OpenShift security constraints.
The main chart for TAINUX Doctor AI. Deploys the FastAPI diagnosis backend, the Next.js frontend and the read-only ClusterRole in a single Helm release. Suitable for standard Kubernetes clusters and OKD.
tainux-system by defaultChart variant optimized for Red Hat OpenShift. Includes SecurityContextConstraints, Route resources instead of Ingress and compatibility with OpenShift RBAC and namespace policies.
Standalone RBAC chart for environments where cluster roles are managed separately from application workloads. Installs only the ClusterRole and ClusterRoleBinding required by TAINUX Doctor AI.
All charts are configurable through standard Helm values. The most common parameters are listed below. A full values reference is available in the chart repository.
Set llm.provider to openai or ollama. For OpenAI, provide the API key via a Kubernetes Secret reference. For open-source models, point to your Ollama or compatible endpoint.
Set rbac.readOnly=true to enforce read-only ClusterRole (default). Set rbac.create=false to skip RBAC creation when using the standalone tainux-doctor-rbac chart.
Enable Kubernetes Ingress with ingress.enabled=true and set ingress.host. On OpenShift, use the tainux-doctor-openshift chart which creates a Route resource automatically.
Configure CPU and memory requests and limits for the backend and frontend pods via backend.resources and frontend.resources. Default values are suitable for most development and staging environments.
The TAINUX Doctor AI chart installs a self-contained set of Kubernetes resources. No sidecars, no daemonsets, no privileged containers. All resources are deployed into a single dedicated namespace.
A single Helm release installs all required resources into a dedicated namespace. The chart manages the full lifecycle: install, upgrade, rollback and uninstall.
Add the TAINUX Helm repository, choose the chart for your environment and install. The cluster is ready to diagnose immediately after deployment.
# Add TAINUX Helm repository
helm repo add tainux \
https://charts.tainux.io
helm repo update
# Install on Kubernetes or OKD
helm install \
tainux-doctor \
tainux/doctor \
-n tainux-system \
--create-namespace \
--set rbac.readOnly=true \
--set llm.provider=openai# Install on Red Hat OpenShift
helm repo add tainux \
https://charts.tainux.io
helm repo update
# Use the OpenShift variant
helm install \
tainux-doctor \
tainux/doctor-openshift \
-n tainux-system \
--create-namespace \
--set rbac.readOnly=true \
--set route.enabled=true# Minimal values.yaml example
llm:
provider: openai
secretRef: openai-secret
rbac:
readOnly: true
create: true
ingress:
enabled: true
host: doctor.example.com
backend:
replicas: 1
resources:
requests:
memory: 256Mi
cpu: 100mTAINUX Software builds and maintains the official Helm charts for TAINUX Doctor AI. Charts are versioned following semantic versioning, tested against Kubernetes, OKD and Red Hat OpenShift releases and published to the public TAINUX chart repository at https://charts.tainux.io.
Each chart release is aligned with a TAINUX Doctor AI application release. Chart changelogs are published in the GitHub repository and include upgrade notes for breaking changes between versions.
Charts are designed for production use. Default values enforce read-only RBAC, namespace isolation and no privileged containers. OpenShift-specific constraints are handled automatically by the dedicated chart variant.
Open an issue on GitHub, ask a deployment question or request support for your specific Kubernetes environment. Answered by engineers within one business day.