/docs/6_configuration_and_deployments/configurations/components/function-runner-config/Recent content in Function Runner on Porch DocumentationHugoen-us/docs/6_configuration_and_deployments/configurations/components/function-runner-config/function-configuration/Mon, 01 Jan 0001 00:00:00 +0000/docs/6_configuration_and_deployments/configurations/components/function-runner-config/function-configuration/<p><strong>FunctionConfig</strong> is the custom resource that configures how a function image is executed: a pod, a binary, a Go call, or any combination of the three. For how these resources are created during install, see <a href="/docs/3_getting_started/installing-porch/">Installing Porch</a> and <a href="/docs/6_configuration_and_deployments/deployments/catalog-deployment/">Catalog Deployment</a>.</p> <h2 id="how-components-consume-functionconfig">How components consume FunctionConfig<a class="td-heading-self-link" href="#how-components-consume-functionconfig" aria-label="Heading self-link"></a></h2> <p>The same CRD is watched independently by three processes. Each process runs an embedded reconciler that copies matching FunctionConfig objects into its own in-memory store and records the generation it applied on the resource status:</p>