Copy page

Version: v0.5.0

On Self-Hosted Kubernetes

Install the Agent Manager on a self-hosted Kubernetes cluster with OpenChoreo.

Overview

This guide walks through deploying the Agent Manager on a self-hosted Kubernetes cluster. The installation consists of two main phases:

OpenChoreo Platform Setup - Install the base OpenChoreo platform (Control Plane, Data Plane, Build Plane, Observability Plane)
Agent Manager Installation - Install the Agent Manager components on top of OpenChoreo

Important: This setup is designed for development and exploration. For production deployments, additional security hardening, TLS configuration, and identity provider integration are required.

Prerequisites

Hardware Requirements

Minimum Resources:
- 8 GB RAM
- 4 CPU cores
- ~10 GB free disk space

Required Tools

Before installation, ensure you have the following tools installed:

Docker (v26.0+) - Container runtime
kubectl (v1.32+) - Kubernetes command-line tool
helm (v3.12+) - Package manager for Kubernetes
k3d (v5.8+) - Lightweight Kubernetes for local development (optional, for local clusters)

Platform-Specific Notes:

macOS users: Use Colima with VZ and Rosetta support
Rancher Desktop users: Must use containerd and configure HTTP registry access for the Build Plane

Verify tools are installed:

docker --version
kubectl version --client
helm version
k3d version  # If using k3d for local development

For Existing Kubernetes Clusters

If you have an existing Kubernetes cluster, ensure:

Kubernetes 1.32+ is running
cert-manager is pre-installed
An ingress controller is configured
Cluster has minimum 8 GB RAM and 4 CPU cores

Permissions

Ensure you have sufficient permissions to:

Create namespaces
Deploy Helm charts
Create and manage Kubernetes resources (Deployments, Services, ConfigMaps, Secrets)
Access cluster resources via kubectl

Phase 1: OpenChoreo Platform Setup

The Agent Manager requires a complete OpenChoreo platform installation.

📚 Base Installation Guide: OpenChoreo Self-Hosted Kubernetes Installation

Important: Agent Manager-Specific Configuration

While following the OpenChoreo installation guide, use the Agent Manager-optimized values files for certain components:

Component	Required Values File
Build Plane	values-bp.yaml
Observability Plane	values-op.yaml
Control Plane	values-cp.yaml
Data Plane	values-dp.yaml

Installation Steps

Follow the OpenChoreo Self-Hosted Kubernetes Installation Guide with the following Agent Manager-specific configurations.

Step 1: Install OpenChoreo Control Plane

# Install Control Plane (optional: use Agent Manager values file)
helm install openchoreo-control-plane \
  oci://ghcr.io/openchoreo/helm-charts/openchoreo-control-plane \
  --version 0.13.0 \
  --namespace openchoreo-control-plane \
  --create-namespace \
  --timeout 600s \
  --values https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/single-cluster/values-cp.yaml

# Wait for Control Plane to be ready
kubectl wait --for=condition=Available \
  deployment --all -n openchoreo-control-plane --timeout=600s

Note: The values file configures the base domain, Thunder identity provider, and other Control Plane settings optimized for Agent Manager.

Step 2: Install OpenChoreo Data Plane

# Install Data Plane (optional: use Agent Manager values file)
helm install openchoreo-data-plane \
  oci://ghcr.io/openchoreo/helm-charts/openchoreo-data-plane \
  --version 0.13.0 \
  --namespace openchoreo-data-plane \
  --create-namespace \
  --timeout 600s \
  --values https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/single-cluster/values-dp.yaml

# Wait for Data Plane to be ready
kubectl wait --for=condition=Available \
  deployment --all -n openchoreo-data-plane --timeout=600s

Note: Follow the OpenChoreo guide to register the Data Plane with the Control Plane (creating DataPlane CR with CA certificates).

Step 3: Install OpenChoreo Build Plane

⚠️ Required: Use Agent Manager's Build Plane values file to configure the registry endpoint correctly:

# Install Docker Registry first
helm upgrade --install registry docker-registry \
  --repo https://twuni.github.io/docker-registry.helm \
  --namespace openchoreo-build-plane \
  --create-namespace \
  --set persistence.enabled=true \
  --set persistence.size=10Gi \
  --set service.type=LoadBalancer \
  --timeout 120s

# Install Build Plane with Agent Manager-specific registry configuration
helm install openchoreo-build-plane \
  oci://ghcr.io/openchoreo/helm-charts/openchoreo-build-plane \
  --version 0.13.0 \
  --namespace openchoreo-build-plane \
  --timeout 600s \
  --values https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/single-cluster/values-bp.yaml

# Wait for Build Plane to be ready
kubectl wait --for=condition=Available \
  deployment --all -n openchoreo-build-plane --timeout=600s

This configures the registry endpoint as host.k3d.internal:10082, which is required for Agent Manager Build Extension compatibility.

Note: Follow the OpenChoreo guide to register the Build Plane with the Control Plane (creating BuildPlane CR with CA certificates).

Step 4: Install OpenChoreo Observability Plane

Recommended: Use Agent Manager's Observability Plane values file, and apply the custom OpenTelemetry Collector ConfigMap:

# Create namespace
kubectl create namespace openchoreo-observability-plane

# Apply custom OpenTelemetry Collector ConfigMap (required for Agent Manager)
kubectl apply -f https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/values/oc-collector-configmap.yaml \
  -n openchoreo-observability-plane

# Install Observability Plane with Agent Manager-optimized configuration
helm install openchoreo-observability-plane \
  oci://ghcr.io/openchoreo/helm-charts/openchoreo-observability-plane \
  --version 0.13.0 \
  --namespace openchoreo-observability-plane \
  --timeout 900s \
  --values https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/single-cluster/values-op.yaml

# Wait for deployments to be ready
kubectl wait --for=condition=Available \
  deployment --all -n openchoreo-observability-plane --timeout=900s

# Wait for StatefulSets (OpenSearch) to be ready
for sts in $(kubectl get statefulset -n openchoreo-observability-plane -o name 2>/dev/null); do
  kubectl rollout status "${sts}" -n openchoreo-observability-plane --timeout=900s
done

Note: Follow the OpenChoreo guide to register the Observability Plane with the Control Plane (creating ObservabilityPlane CR with CA certificates).

Step 5: Configure Observability Integration

Link the Data Plane and Build Plane to the Observability Plane:

# Configure DataPlane to use observability plane
kubectl patch dataplane default -n default --type merge \
  -p '{"spec":{"observabilityPlaneRef":"default"}}'

# Configure BuildPlane to use observability plane
kubectl patch buildplane default -n default --type merge \
  -p '{"spec":{"observabilityPlaneRef":"default"}}'

For detailed plane registration steps (extracting CA certificates and creating plane CRs), refer to the OpenChoreo Self-Hosted Kubernetes Guide.

Verify OpenChoreo Installation

Before proceeding to Agent Manager installation, verify all OpenChoreo components are running:

# Verify all namespaces and pods
kubectl get namespace openchoreo-control-plane openchoreo-data-plane openchoreo-build-plane openchoreo-observability-plane
kubectl get pods -n openchoreo-control-plane
kubectl get pods -n openchoreo-data-plane
kubectl get pods -n openchoreo-build-plane
kubectl get pods -n openchoreo-observability-plane

# Check OpenSearch is available (required for Agent Manager)
kubectl get pods -n openchoreo-observability-plane -l app=opensearch

# Verify plane registrations
kubectl get dataplane,buildplane,observabilityplane -n default

All pods should be in Running or Completed state before proceeding.

Phase 2: Agent Manager Installation

Now that OpenChoreo is installed, you can install the Agent Manager components.

The Agent Manager installation consists of four main components:

Agent Manager - Core platform (PostgreSQL, API, Console)
Platform Resources Extension - Default Organization, Project, Environment, DeploymentPipeline
Observability Extension - Traces Observer service
Build Extension - Workflow templates for building container images

Configuration Variables

Set the following environment variables before installation (if not already set from Phase 1):

# Helm chart registry
export HELM_CHART_REGISTRY="ghcr.io/wso2"

# Namespaces
export AMP_NS="wso2-amp"
export BUILD_CI_NS="openchoreo-build-plane"
export OBSERVABILITY_NS="openchoreo-observability-plane"
export DEFAULT_NS="default"
export DATA_PLANE_NS="openchoreo-data-plane"

Step 1: Install Gateway Operator

The Gateway Operator manages API Gateway resources and enables secure trace ingestion to the Observability Plane.

# Install Gateway Operator
helm install gateway-operator \
  oci://ghcr.io/wso2/api-platform/helm-charts/gateway-operator \
  --version 0.2.0 \
  --namespace ${DATA_PLANE_NS} \
  --set logging.level=debug \
  --set gateway.helm.chartVersion=0.3.0 \
  --timeout 600s

# Wait for Gateway Operator deployment
kubectl wait --for=condition=Available \
  deployment -l app.kubernetes.io/name=gateway-operator \
  -n ${DATA_PLANE_NS} --timeout=300s

Apply Gateway Operator Configuration:

This configuration sets up API authentication (using JWT/JWKS) and rate limiting policies:

# Apply Gateway Operator configuration
kubectl apply -f https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/values/api-platform-operator-full-config.yaml

Create Gateway and API Resources:

Deploy the observability gateway and trace API endpoint:

# Apply Observability Gateway
kubectl apply -f https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/values/obs-gateway.yaml

# Wait for Gateway to be programmed
kubectl wait --for=condition=Programmed \
  gateway/obs-gateway -n ${DATA_PLANE_NS} --timeout=180s

# Apply OTEL Collector RestApi
kubectl apply -f https://raw.githubusercontent.com/wso2/agent-manager/amp/v0.5.0/deployments/values/otel-collector-rest-api.yaml

# Wait for RestApi to be programmed
kubectl wait --for=condition=Programmed \
  restapi/traces-api-secure -n ${DATA_PLANE_NS} --timeout=120s

The observability gateway will be accessible for trace ingestion at http://localhost:22893/otel (HTTP) or https://localhost:22894/otel (HTTPS) when port-forwarded.

Step 2: Install AMP Thunder Extension

The AMP Thunder Extension provides additional identity and authentication features for the Agent Management Platform.

# Set Thunder namespace
export THUNDER_NS="amp-thunder"

# Install AMP Thunder Extension
helm install amp-thunder-extension \
  oci://${HELM_CHART_REGISTRY}/wso2-amp-thunder-extension \
  --version 0.5.0 \
  --namespace ${THUNDER_NS} \
  --create-namespace \
  --timeout 1800s

Note: This extension is optional. The platform will function without it, but Thunder extension features may not be available.

Step 3: Install Agent Manager

The core platform includes:

PostgreSQL database
Agent Manager Service (API)
Console (Web UI)

Installation:

# Install the platform Helm chart with instrumentation URL configured
helm install amp \
  oci://${HELM_CHART_REGISTRY}/wso2-agent-manager \
  --version 0.5.0 \
  --namespace ${AMP_NS} \
  --create-namespace \
  --set console.config.instrumentationUrl="http://localhost:22893/otel" \
  --timeout 1800s

Note: The console.config.instrumentationUrl is configured to point to the observability gateway for trace ingestion. Update this URL if you're using a different endpoint or exposing the gateway differently.

Wait for components to be ready:

# Wait for PostgreSQL StatefulSet
kubectl wait --for=jsonpath='{.status.readyReplicas}'=1 \
  statefulset/amp-postgresql -n ${AMP_NS} --timeout=600s

# Wait for Agent Manager Service
kubectl wait --for=condition=Available \
  deployment/amp-api -n ${AMP_NS} --timeout=600s

# Wait for Console
kubectl wait --for=condition=Available \
  deployment/amp-console -n ${AMP_NS} --timeout=600s

Step 4: Install Platform Resources Extension

The Platform Resources Extension creates default resources:

Default Organization
Default Project
Environment
DeploymentPipeline

Installation:

# Install Platform Resources Extension
helm install amp-platform-resources \
  oci://${HELM_CHART_REGISTRY}/wso2-amp-platform-resources-extension \
  --version 0.5.0 \
  --namespace ${DEFAULT_NS} \
  --timeout 1800s

Note: This extension is non-fatal if installation fails. The platform will function, but default resources may not be available.

Step 5: Install Observability Extension

The observability extension includes the Traces Observer service for querying traces from OpenSearch.

Installation:

# Set configuration variables
export OBSERVABILITY_NS="openchoreo-observability-plane"

# Install observability Helm chart
helm install amp-observability-traces \
  oci://${HELM_CHART_REGISTRY}/wso2-amp-observability-extension \
  --version 0.5.0 \
  --namespace ${OBSERVABILITY_NS} \
  --timeout 1800s

Wait for Traces Observer to be ready:

# Wait for Traces Observer deployment
kubectl wait --for=condition=Available \
  deployment/amp-traces-observer -n ${OBSERVABILITY_NS} --timeout=600s

Note: This extension is non-fatal if installation fails. The platform will function, but observability features may not work.

Step 6: Install Build Extension

Install workflow templates for building container images. The Build Extension must be configured to use the same container registry that was installed by OpenChoreo Build Plane.

Registry Configuration:

In Phase 1, Step 4, you installed OpenChoreo Build Plane which deployed a container registry with the endpoint host.k3d.internal:10082 (configured in deployments/single-cluster/values-bp.yaml).

The Agent Manager Build Extension must point to this same registry endpoint:

# Set the registry endpoint (must match OpenChoreo Build Plane configuration)
# This value comes from the values-bp.yaml used in Phase 1, Step 4
export REGISTRY_ENDPOINT="host.k3d.internal:10082"

# Install Build Extension with the same registry endpoint
helm install build-workflow-extensions \
  oci://${HELM_CHART_REGISTRY}/wso2-amp-build-extension \
  --version 0.5.0 \
  --namespace ${BUILD_CI_NS} \
  --set global.registry.endpoint=${REGISTRY_ENDPOINT} \
  --timeout 1800s

If You Used a Different Registry Endpoint:

If you installed OpenChoreo Build Plane with a different registry endpoint configuration (not using the provided values-bp.yaml), make sure to use the same endpoint you configured in the Build Plane installation.

Common alternative endpoints:

Docker Desktop / Colima: host.docker.internal:10082
Node IP based: <node-ip>:10082
In-cluster only: registry.openchoreo-build-plane.svc.cluster.local:5000

Verification:

You can verify the registry endpoint configured in your OpenChoreo Build Plane by checking the workflow templates:

kubectl get clusterworkflowtemplate ballerina-buildpack-ci -o yaml | grep REGISTRY_ENDPOINT

Note: This extension is optional. The platform will function without it, but build CI features may not work.

Verification

Verify all components are installed and running:

# 1. Check OpenChoreo Platform Components
echo "=== OpenChoreo Platform Status ==="
kubectl get pods -n openchoreo-control-plane
kubectl get pods -n openchoreo-data-plane
kubectl get pods -n openchoreo-build-plane
kubectl get pods -n openchoreo-observability-plane

# 2. Check Agent Manager Components
echo "=== Agent Manager Status ==="
kubectl get pods -n wso2-amp

# 3. Check Observability Extension
echo "=== Observability Extension Status ==="
kubectl get pods -n openchoreo-observability-plane | grep -E "amp-traces-observer"

# 4. Check Build Extension
echo "=== Build Extension Status ==="
kubectl get pods -n openchoreo-build-plane | grep build-workflow

# 5. Check Gateway Operator
echo "=== Gateway Operator Status ==="
kubectl get pods -n openchoreo-data-plane -l app.kubernetes.io/name=gateway-operator

# 6. Check Gateway and API Resources
echo "=== Gateway and API Resources ==="
kubectl get gateway obs-gateway -n openchoreo-data-plane
kubectl get restapi traces-api-secure -n openchoreo-data-plane

# 7. Check Helm Releases
echo "=== Helm Releases ==="
helm list -n openchoreo-control-plane
helm list -n openchoreo-data-plane
helm list -n openchoreo-build-plane
helm list -n openchoreo-observability-plane
helm list -n wso2-amp
helm list -n default

# 8. Verify Plane Registrations
echo "=== Plane Registrations ==="
kubectl get dataplane default -n default -o jsonpath='{.spec.observabilityPlaneRef}'
kubectl get buildplane default -n default -o jsonpath='{.spec.observabilityPlaneRef}'

Expected output should show all pods in Running or Completed state.

Access the Platform

Access via Ingress (Recommended)

If you're using the provided k3d/Traefik ingress configuration, the services are accessible directly:

OpenChoreo Platform:

Console: http://openchoreo.localhost:8080
API: http://api.openchoreo.localhost:8080
Default credentials: admin@openchoreo.dev / Admin@123

Agent Manager:

Console: Access through OpenChoreo console or via port forwarding (see below)
API: Access via port forwarding (see below)

Port Forwarding (Alternative)

For direct access or non-ingress setups, use port forwarding:

# Agent Manager Console (port 3000)
kubectl port-forward -n wso2-amp svc/amp-console 3000:3000 &

# Agent Manager API (port 9000)
kubectl port-forward -n wso2-amp svc/amp-api 9000:9000 &

# Observability Gateway HTTP (port 22893)
kubectl port-forward -n openchoreo-data-plane svc/obs-gateway-gateway-router 22893:22893 &

# Observability Gateway HTTPS (port 22894)
kubectl port-forward -n openchoreo-data-plane svc/obs-gateway-gateway-router 22894:22894 &

Access URLs (Port Forwarding)

After port forwarding is set up:

Agent Manager Console: http://localhost:3000
Agent Manager API: http://localhost:9000
Observability Gateway (HTTP): http://localhost:22893/otel
Observability Gateway (HTTPS): https://localhost:22894/otel

Handling Self-Signed Certificate Issues (HTTPS)

If you need to use the HTTPS endpoint for OTEL exporters and encounter self-signed certificate issues, you can extract and use the certificate authority (CA) certificate from the cluster:

# Extract the CA certificate from the Kubernetes secret
kubectl get secret obs-gateway-gateway-controller-tls \
  -n openchoreo-data-plane \
  -o jsonpath='{.data.ca\.crt}' | base64 --decode > ca.crt

# Export the certificate path for OTEL exporters (use absolute path to the ca.crt file)
export OTEL_EXPORTER_OTLP_CERTIFICATE=$(pwd)/ca.crt

Custom Configuration

Using Custom Values File

Create a custom values file (e.g., custom-values.yaml):

agentManagerService:
  replicaCount: 2
  resources:
    requests:
      memory: 512Mi
      cpu: 500m

console:
  replicaCount: 2

postgresql:
  auth:
    password: "my-secure-password"

Install with custom values:

helm install amp \
  oci://${HELM_CHART_REGISTRY}/wso2-agent-manager \
  --version 0.5.0 \
  --namespace ${AMP_NS} \
  --create-namespace \
  --timeout 1800s \
  -f custom-values.yaml

Production Considerations

Important: This installation is designed for development and exploration only. For production deployments, you must:

Replace default credentials with a proper identity provider (OAuth, SAML, etc.)
Configure TLS certificates - Replace self-signed certificates with proper CA-signed certificates
Implement multi-cluster connectivity - Configure proper networking between planes
Set up persistent observability storage - Configure persistent volumes and backup strategies for OpenSearch
Resource sizing - Adjust resource requests/limits based on workload requirements
High availability - Deploy multiple replicas of critical components
Monitoring and alerting - Set up proper monitoring for production workloads
Security hardening - Apply security best practices (network policies, RBAC, pod security policies)

Troubleshooting

Common Issues

Pods stuck in Pending state:

# Check resource availability
kubectl describe pod <pod-name> -n <namespace>

# Check node resources
kubectl top nodes

Gateway not becoming Programmed:

# Check Gateway Operator logs
kubectl logs -n openchoreo-data-plane -l app.kubernetes.io/name=gateway-operator

# Check Gateway status
kubectl describe gateway obs-gateway -n openchoreo-data-plane

Plane registration issues:

# Verify planeID matches between DataPlane CR and Helm values
kubectl get dataplane default -n default -o yaml

# Check Control Plane logs
kubectl logs -n openchoreo-control-plane -l app.kubernetes.io/name=openchoreo-control-plane

OpenSearch connectivity issues:

# Check OpenSearch pods
kubectl get pods -n openchoreo-observability-plane -l app=opensearch

# Test OpenSearch connectivity
kubectl run -it --rm debug --image=curlimages/curl --restart=Never -- \
  curl -v http://opensearch.openchoreo-observability-plane.svc.cluster.local:9200

Additional Configuration

k3d Cluster-Specific Setup (Optional)

If you're using k3d and need to ensure host.k3d.internal DNS resolution works correctly, configure CoreDNS:

# Get the gateway IP for the k3d network
CLUSTER_NAME="amp-local"  # Adjust to your cluster name
GATEWAY_IP=$(docker network inspect "k3d-${CLUSTER_NAME}" \
  -f '{{range .IPAM.Config}}{{.Gateway}}{{end}}' 2>/dev/null || true)

# Add host.k3d.internal to CoreDNS NodeHosts
if [ -n "$GATEWAY_IP" ]; then
  CURRENT_HOSTS=$(kubectl get cm coredns -n kube-system \
    -o jsonpath='{.data.NodeHosts}')

  # Check if entry already exists
  if ! echo "$CURRENT_HOSTS" | grep -q "host.k3d.internal"; then
    echo "Adding host.k3d.internal to CoreDNS..."
    kubectl patch configmap coredns -n kube-system --type merge \
      -p "{\"data\":{\"NodeHosts\":\"${CURRENT_HOSTS}\n${GATEWAY_IP} host.k3d.internal\n\"}}"

    # Restart CoreDNS
    kubectl rollout restart deployment coredns -n kube-system
    kubectl rollout status deployment/coredns -n kube-system --timeout=60s
  fi
fi

Reference Configuration Files

All configuration values files used in this guide are available in the repository:

Control Plane Values: deployments/single-cluster/values-cp.yaml
Data Plane Values: deployments/single-cluster/values-dp.yaml
Build Plane Values: deployments/single-cluster/values-bp.yaml
Observability Plane Values: deployments/single-cluster/values-op.yaml
Gateway Operator Config: deployments/values/api-platform-operator-full-config.yaml
Observability Gateway: deployments/values/obs-gateway.yaml
OTEL Collector ConfigMap: deployments/values/oc-collector-configmap.yaml
OTEL Collector RestApi: deployments/values/otel-collector-rest-api.yaml

You can customize these files for your specific deployment needs.

Overview​

Prerequisites​

Hardware Requirements​

Required Tools​

For Existing Kubernetes Clusters​

Permissions​

Phase 1: OpenChoreo Platform Setup​

Important: Agent Manager-Specific Configuration​

Installation Steps​

Step 1: Install OpenChoreo Control Plane​

Step 2: Install OpenChoreo Data Plane​

Step 3: Install OpenChoreo Build Plane​

Step 4: Install OpenChoreo Observability Plane​

Step 5: Configure Observability Integration​

Verify OpenChoreo Installation​

Phase 2: Agent Manager Installation​

Configuration Variables​

Step 1: Install Gateway Operator​

Step 2: Install AMP Thunder Extension​

Step 3: Install Agent Manager​

Step 4: Install Platform Resources Extension​

Step 5: Install Observability Extension​

Step 6: Install Build Extension​

Verification​

Access the Platform​

Access via Ingress (Recommended)​

Port Forwarding (Alternative)​

Access URLs (Port Forwarding)​

Handling Self-Signed Certificate Issues (HTTPS)​

Custom Configuration​

Using Custom Values File​

Production Considerations​

Troubleshooting​

Common Issues​

Additional Configuration​

k3d Cluster-Specific Setup (Optional)​

Reference Configuration Files​

Overview

Prerequisites

Hardware Requirements

Required Tools

For Existing Kubernetes Clusters

Permissions

Phase 1: OpenChoreo Platform Setup

Important: Agent Manager-Specific Configuration

Installation Steps

Step 1: Install OpenChoreo Control Plane

Step 2: Install OpenChoreo Data Plane

Step 3: Install OpenChoreo Build Plane

Step 4: Install OpenChoreo Observability Plane

Step 5: Configure Observability Integration

Verify OpenChoreo Installation

Phase 2: Agent Manager Installation

Configuration Variables

Step 1: Install Gateway Operator

Step 2: Install AMP Thunder Extension

Step 3: Install Agent Manager

Step 4: Install Platform Resources Extension

Step 5: Install Observability Extension

Step 6: Install Build Extension

Verification

Access the Platform

Access via Ingress (Recommended)

Port Forwarding (Alternative)

Access URLs (Port Forwarding)

Handling Self-Signed Certificate Issues (HTTPS)

Custom Configuration

Using Custom Values File

Production Considerations

Troubleshooting

Common Issues

Additional Configuration

k3d Cluster-Specific Setup (Optional)

Reference Configuration Files