Git Authentication

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:

1. Basic Authentication - Username and password or Personal Access Token (post-deployment)
2. Bearer Token Authentication - Token-based authentication (post-deployment)
3. 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:

• Exist in the same namespace as the Repository CR
• Have data keys named username and password
• Be of type kubernetes.io/basic-auth

The password field can contain a base64-encoded Personal Access Token instead of a password.

Create Basic Auth Secret

kubectl create secret generic git-auth-secret \
  --namespace=default \
  --from-literal=username=your-username \
  --from-literal=password=your-password \
  --type=kubernetes.io/basic-auth

Repository Configuration

apiVersion: config.porch.kpt.dev/v1alpha1
kind: Repository
metadata:
  name: example-repo
  namespace: default
spec:
  type: git
  git:
    repo: https://github.com/example/repo.git
    branch: main
    secretRef:
      name: git-auth-secret

2. Bearer Token Authentication

Uses token-based authentication (e.g., GitHub PAT, GitLab token). The secret must:

• Exist in the same namespace as the Repository CR
• Have a data key named bearerToken
• Be of type Opaque

Create Bearer Token Secret

kubectl create secret generic git-token-secret \
  --namespace=default \
  --from-literal=bearerToken=your-token \
  --type=Opaque

Repository Configuration

apiVersion: config.porch.kpt.dev/v1alpha1
kind: Repository
metadata:
  name: example-repo
  namespace: default
spec:
  type: git
  git:
    repo: https://github.com/example/repo.git
    branch: main
    secretRef:
      name: git-token-secret

3. HTTPS/TLS Configuration

For Git repositories with custom TLS certificates. The CA bundle secret must:

• Exist in the same namespace as the Repository CR
• Be named exactly <namespace>-ca-bundle
• Have a data key named ca.crt containing the certificate chain

Enable TLS Support

Add the --use-git-cabundle=true argument to the Porch Server deployment.

Create CA Bundle Secret

The secret must be named <namespace>-ca-bundle:

kubectl create secret generic default-ca-bundle \
  --namespace=default \
  --from-file=ca.crt=/path/to/ca-certificate.crt

Repository Configuration

apiVersion: config.porch.kpt.dev/v1alpha1
kind: Repository
metadata:
  name: secure-repo
  namespace: default
spec:
  type: git
  git:
    repo: https://secure-git.example.com/repo.git
    branch: main
    secretRef:
      name: git-auth-secret

Authentication Behavior

Credential Caching

HTTP Request Examples

Basic Authentication:

Authorization: Basic bmVwaGlvOnNlY3JldA==

Bearer Token:

Authorization: Bearer your-token-here

Common Use Cases

• GitHub: Use Personal Access Token with bearer token authentication
• GitLab: Use Project Access Token or Personal Access Token
• Enterprise Git: Use basic authentication with username/password
• Self-hosted Git: Use TLS configuration for custom certificates

Using porchctl CLI

You can create repositories with basic authentication using the porchctl command:

# Basic authentication
porchctl repo reg my-repo -n default https://github.com/example/repo.git \
  --repo-basic-username=username \
  --repo-basic-password=password

# This creates both the secret and Repository CR automatically