<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Configurations on Porch Documentation</title><link>/docs/6_configuration_and_deployments/configurations/</link><description>Recent content in Configurations on Porch Documentation</description><generator>Hugo</generator><language>en-us</language><atom:link href="/docs/6_configuration_and_deployments/configurations/index.xml" rel="self" type="application/rss+xml"/><item><title>Repository Sync</title><link>/docs/6_configuration_and_deployments/configurations/repository-sync/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/6_configuration_and_deployments/configurations/repository-sync/</guid><description>&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Documentation Location&lt;/h4>

 This documentation is currently located in the system configuration section but should be moved to a more logical location as it&amp;rsquo;s about configuring individual Repository resources, not system-wide settings. This may be relocated in future documentation updates.

&lt;/div>

&lt;h2 id="sync-configuration-fields">Sync Configuration Fields&lt;/h2>&lt;p>The &lt;code>spec.sync&lt;/code> field in a Repository CR controls synchronization behavior with the external repository. Repositories without sync configuration use the system default for periodic synchronization (default 1 hour, configurable via &lt;code>--repositories.full-sync-frequency&lt;/code> flag - see 
&lt;a href="/docs/6_configuration_and_deployments/configurations/components/porch-controllers-config/#repository-controller-configuration">Repository Controller Configuration&lt;/a>.&lt;/p></description></item><item><title>Cache Configuration</title><link>/docs/6_configuration_and_deployments/configurations/cache/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/6_configuration_and_deployments/configurations/cache/</guid><description>&lt;p>Porch supports two caching mechanisms for storing package metadata. Choose based on your deployment scale and infrastructure.&lt;/p>
&lt;h2 id="cache-types">Cache Types&lt;/h2>&lt;h3 id="cr-cache-default">CR Cache (Default)&lt;/h3>&lt;p>Uses Custom Resources for metadata tracking while package content is served through Porch&amp;rsquo;s aggregated API server. Suitable for development and smaller deployments.&lt;/p>
&lt;p>&lt;strong>Characteristics:&lt;/strong>&lt;/p>
&lt;ul>
&lt;li>No external database required&lt;/li>
&lt;li>Metadata stored in Kubernetes etcd via Custom Resources&lt;/li>
&lt;li>Package content served through aggregated API server&lt;/li>
&lt;li>Automatic backup with cluster backups&lt;/li>
&lt;li>Simple operational model&lt;/li>
&lt;/ul>
&lt;p>&lt;strong>Best For:&lt;/strong>&lt;/p></description></item><item><title>OpenTelemetry Configuration</title><link>/docs/6_configuration_and_deployments/configurations/opentelemetry/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/6_configuration_and_deployments/configurations/opentelemetry/</guid><description>&lt;h2 id="overview">Overview&lt;/h2>&lt;p>Porch supports OpenTelemetry observability through the 
&lt;a href="https://pkg.go.dev/go.opentelemetry.io/contrib/exporters/autoexport" target="_blank">autoexport package&lt;/a>, which provides automatic configuration of metrics and traces exporters via environment variables. This enables seamless integration with various observability backends including OTLP collectors, Prometheus, and Jaeger.&lt;/p>
&lt;p>All Porch components (porch-server, porch-controllers, function-runner, and wrapper-server) support OpenTelemetry configuration through standardized environment variables as defined by the 
&lt;a href="https://opentelemetry.io/docs/specs/otel/configuration/sdk-environment-variables/" target="_blank">OpenTelemetry specification&lt;/a>.&lt;/p>


&lt;div class="alert alert-primary" role="alert">
&lt;h4 class="alert-heading">Note&lt;/h4>

 &lt;strong>Current Implementation Status&lt;/strong>: Porch currently implements metrics and traces export. Logs export is not supported.

&lt;/div>

&lt;h2 id="traces-configuration">Traces Configuration&lt;/h2>&lt;h3 id="otlp-trace-export">OTLP Trace Export&lt;/h3>&lt;p>Export traces to an OpenTelemetry Protocol (OTLP) collector using either HTTP or gRPC protocols.&lt;/p></description></item></channel></rss>