Saltar al contenido principal

Try with Helm

This page describes how to deploy Casdoor on Kubernetes using Helm.

Prerrequisitos

  • A running Kubernetes cluster (1.19+)
  • Helm v3.8+

Installation

Step 1: Install the Casdoor chart

Install the Casdoor Helm chart:

helm install casdoor oci://registry-1.docker.io/casbin/casdoor-helm-charts --version <version>

To install with a custom values file:

helm install casdoor oci://registry-1.docker.io/casbin/casdoor-helm-charts \
--version <version> \
-f my-values.yaml

Step 2: Access Casdoor

After installation, use the service URL provided by your cluster to access Casdoor.

Customization

Override values.yaml to customize the deployment. Key parameters:

ParámetroDescripciónValor Predeterminado
replicaCountNúmero de réplicas de la aplicación Casdoor a ejecutar.1
image.repositoryRepositorio para la imagen Docker de Casdoor.casbin
image.nameNombre de la imagen Docker de Casdoor.casdoor
image.pullPolicyPolítica de extracción para la imagen Docker de Casdoor.IfNotPresent
image.tagEtiqueta para la imagen Docker de Casdoor.""
configConfiguraciones de ajustes para la aplicación Casdoor.See values.yaml
database.driverDatabase driver to use (mysql, postgres, cockroachdb, sqlite).sqlite
database.userNombre de usuario de la base de datos.""
database.passwordContraseña de la base de datos.""
database.hostHost de la base de datos.""
database.portPuerto de la base de datos.""
database.databaseNameNombre de la base de datos utilizada por Casdoor.casdoor
database.sslModeModo SSL para la conexión a la base de datos.disable
service.typeType of Kubernetes service (ClusterIP, NodePort, LoadBalancer).ClusterIP
service.portNúmero de puerto para el servicio de Casdoor.8000
ingress.enabledSi habilitar Ingress para Casdoor.false
ingress.annotationsAnotaciones para el recurso Ingress.{}
ingress.hostsHostnames para el recurso Ingress.[]
resourcesSolicitudes y límites de recursos para el contenedor de Casdoor.{}
autoscaling.enabledSi habilitar el Escalador Horizontal de Pods para Casdoor.false
autoscaling.minReplicasMinimum number of replicas for HPA.1
autoscaling.maxReplicasMaximum number of replicas for HPA.100
autoscaling.targetCPUUtilizationPercentageTarget CPU utilization percentage for HPA.80
nodeSelectorEtiquetas de nodo para la asignación de pods.{}
tolerationsEtiquetas de tolerancia para la asignación de pods.[]
affinityAjustes de afinidad para la asignación de pods.{}
extraContainersEnabledSi habilitar contenedores adicionales de sidecar.false
extraContainersContenedores adicionales de sidecar.""
extraVolumeMountsMontajes de volumen adicionales para el contenedor de Casdoor.[]
extraVolumesVolúmenes adicionales para el contenedor de Casdoor.[]
envFromSecretEnvironment variables from individual Secret keys.[]
envFromConfigmapEnvironment variables from individual ConfigMap keys.[]
envFromEnvironment variables from entire Secrets or ConfigMaps.[]

Exposing Casdoor

Option 1: Ingress (classic)

Enable and configure Ingress:

ingress:
enabled: true
className: nginx
annotations:
cert-manager.io/cluster-issuer: letsencrypt-prod
hosts:
- host: casdoor.example.com
paths:
- path: /
pathType: Prefix
tls:
- secretName: casdoor-tls
hosts:
- casdoor.example.com

Option 2: Gateway API (modern)

The Kubernetes Gateway API is the next-generation successor to Ingress, officially GA since Kubernetes 1.31. It is supported by Istio, Envoy Gateway, Cilium, Kong, NGINX Gateway Fabric, and others.

consejo

Prerequisites

kubectl apply -f https://github.com/kubernetes-sigs/gateway-api/releases/download/v1.2.0/standard-install.yaml

You also need a compatible Gateway controller running in your cluster.

Attach to an existing Gateway

If you already have a Gateway resource in your cluster, point the HTTPRoute at it:

gatewayApi:
enabled: true
parentRefs:
- name: my-gateway
namespace: gateway-system
sectionName: https
hostnames:
- casdoor.example.com

Create a new Gateway (e.g. with Istio)

Let the chart create a Gateway and HTTPRoute together:

gatewayApi:
enabled: true
createGateway: true
hostnames:
- casdoor.example.com
gateway:
gatewayClassName: istio
listeners:
- name: http
protocol: HTTP
port: 80
allowedRoutes:
namespaces:
from: Same

Create a Gateway with HTTP→HTTPS redirect

Enable TLS termination and automatic HTTP-to-HTTPS redirect:

gatewayApi:
enabled: true
createGateway: true
hostnames:
- casdoor.example.com
gateway:
gatewayClassName: istio
listeners:
- name: http
protocol: HTTP
port: 80
allowedRoutes:
namespaces:
from: Same
- name: https
protocol: HTTPS
port: 443
tls:
certificateRefs:
- name: casdoor-tls
kind: Secret
allowedRoutes:
namespaces:
from: Same
httpsRedirect:
enabled: true

Gateway API parameters

ParameterDescriptionDefault
gatewayApi.enabledEnable HTTPRoute creationfalse
gatewayApi.createGatewayAlso create a Gateway resourcefalse
gatewayApi.annotationsAnnotations for the HTTPRoute{}
gatewayApi.labelsExtra labels for the HTTPRoute{}
gatewayApi.parentRefsParent Gateway references[]
gatewayApi.hostnamesHostnames to match (Host header)[]
gatewayApi.rulesRouting rules (matches, filters, backendRefs)PathPrefix /
gatewayApi.gateway.nameGateway name (defaults to chart fullname)""
gatewayApi.gateway.gatewayClassNameGatewayClass name (required when createGateway=true)""
gatewayApi.gateway.listenersGateway listenersHTTP:80
gatewayApi.httpsRedirect.enabledEnable HTTP→HTTPS redirect HTTPRoutefalse
gatewayApi.httpsRedirect.statusCodeRedirect response code301
gatewayApi.httpsRedirect.hostnamesHostnames for redirect route[]
gatewayApi.httpsRedirect.parentRefsOverride parentRefs for redirect route[]

Managing the deployment

Upgrade:

helm upgrade casdoor oci://registry-1.docker.io/casbin/casdoor-helm-charts --version <version>

Uninstall:

helm uninstall casdoor

For more options, see the Helm and Kubernetes documentation.