Porch Server on Porch Documentation

Git Authentication

Mon, 01 Jan 0001 00:00:00 +0000

Authentication Methods

The Porch Server handles interaction with Git repositories through Repository Custom Resources (CRs) that act as a link between the Porch Server and the Git repositories.

Porch Server supports three authentication methods for Git repositories:

Basic Authentication - Username and password or Personal Access Token (post-deployment)
Bearer Token Authentication - Token-based authentication (post-deployment)
HTTPS/TLS Configuration - Custom TLS certificates for self-hosted Git (requires pre-deployment configuration)

1. Basic Authentication

Uses username and password or Personal Access Token (PAT). The secret must:

Pod Templates

Mon, 01 Jan 0001 00:00:00 +0000

The Engine pod evaluator (porch-server and the PackageRevision controller) builds function pods from the PodTemplate/ServiceTemplate objects base-pod-template and base-service-template in the function-pod namespace (default porch-fn-system), plus per-function overrides from the matching FunctionConfig. There is no --function-pod-template flag and no ConfigMap template. This page moved from Function Runner with the pod evaluator.

For how those templates are used during pod creation, see Pod Lifecycle Management.

How templates are applied

On pod creation the Engine:

Private Registries

Mon, 01 Jan 0001 00:00:00 +0000

Note

KPT functions and KRM functions are synonymous terms referring to the same containerized functions.

Configure porch-server to access private container registries for KRM functions. These flags moved from Function Runner with the pod evaluator.

Use Cases

Private registries are commonly used for:

Enterprise environments - Internal Harbor or JFrog registries
Cloud providers - GitHub Container Registry (GHCR), AWS ECR, Azure ACR
Custom functions - Organization-specific KRM functions

Default Public Registries

By default, porch-server uses public registries: