<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Function Runner on Porch Documentation</title><link>/docs/6_configuration_and_deployments/configurations/components/function-runner-config/</link><description>Recent content in Function Runner on Porch Documentation</description><generator>Hugo</generator><language>en-us</language><atom:link href="/docs/6_configuration_and_deployments/configurations/components/function-runner-config/index.xml" rel="self" type="application/rss+xml"/><item><title>Pod Templates</title><link>/docs/6_configuration_and_deployments/configurations/components/function-runner-config/pod-templates/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/6_configuration_and_deployments/configurations/components/function-runner-config/pod-templates/</guid><description>&lt;p&gt;The Function Runner supports customizing the pod specifications used for KRM function evaluation through ConfigMap-based templates. This allows you to configure resource limits, security contexts, node selectors, tolerations, and other pod-level settings for function execution pods.&lt;/p&gt;
&lt;h2 id="overview"&gt;Overview&lt;a class="td-heading-self-link" href="#overview" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;By default, the Function Runner uses an inline pod template with sensible defaults. For advanced use cases requiring customization, you can provide a ConfigMap containing custom pod and service templates. The Function Runner will use these templates when creating function evaluator pods.&lt;/p&gt;</description></item><item><title>Private Registries</title><link>/docs/6_configuration_and_deployments/configurations/components/function-runner-config/private-registries-config/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>/docs/6_configuration_and_deployments/configurations/components/function-runner-config/private-registries-config/</guid><description>&lt;div class="alert alert-primary" role="alert"&gt;&lt;div class="h4 alert-heading" role="heading"&gt;Note&lt;/div&gt;
&lt;p&gt;KPT functions and KRM functions are synonymous terms referring to the same containerized functions.&lt;/p&gt;
&lt;/div&gt;
&lt;p&gt;Configure the Function Runner to access private container registries for KRM functions.&lt;/p&gt;
&lt;h2 id="use-cases"&gt;Use Cases&lt;a class="td-heading-self-link" href="#use-cases" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Private registries are commonly used for:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Enterprise environments&lt;/strong&gt; - Internal Harbor or JFrog registries&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cloud providers&lt;/strong&gt; - GitHub Container Registry (GHCR), AWS ECR, Azure ACR&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom functions&lt;/strong&gt; - Organization-specific KRM functions&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="default-public-registries"&gt;Default Public Registries&lt;a class="td-heading-self-link" href="#default-public-registries" aria-label="Heading self-link"&gt;&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;By default, Function Runner uses public registries:&lt;/p&gt;</description></item></channel></rss>