Configurations

This section covers configuring Porch’s various features and integrations after deployment.

Component Configuration

Components

Configure individual Porch components:

• Porch Server - API server configuration
  • Git Authentication - Git repository authentication
• Porch Controllers - Repository, PackageRevision, and variant controller settings
  • Webhooks - Validating webhooks for resources
• Function Runner - Function execution environment
  • Private Registries - Container registry authentication

OTEL Metrics, Tracing, and Profiling

OpenTelemetry - Tracing, metrics, and profiling configuration

Local Performance Monitoring Deployment - Local Prometheus, Grafana, Grafana Alloy, Jaeger and Pyroscope observability stack.

Core Configuration Options

Cache

Porch supports two caching mechanisms:

• CR Cache (default) - Uses Kubernetes Custom Resources
• Database Cache - Uses PostgreSQL for improved performance

Advanced Integrations

Repository Synchronization

Configure Git repository synchronization with ConfigSync or other GitOps tools.

Configuration Best Practices

• Start with default CR cache for simplicity
• Configure private registries only if using private KRM functions in Function Runner
• Enable tracing in development environments for debugging
• Deploy local performance monitoring when measuring latency or running performance tests
• Use cert-manager for production TLS certificate management
• Set appropriate resource limits for each component