Git Providers

Skipper supports deploying applications from Git repositories. The Git provider is detected automatically from the repository URL.

Supported providers

Provider	Detection	Auth methods
GitHub	github.com in URL	Personal Access Token, SSH key
GitLab (cloud)	gitlab.com in URL	Deploy Token, SSH key
GitLab (self-hosted)	Everything else	Deploy Token, SSH key, CA cert

Authentication

GitHub: Personal Access Token

kip app deploy --name api \
  --git https://github.com/acme/api \
  --git-token github_pat_xxx \
  --port 3000

GitLab: Deploy Token

kip app deploy --name api \
  --git https://gitlab.com/acme/api \
  --git-token gldt-xxx \
  --port 3000

SSH key (any provider)

kip app deploy --name api \
  --git git@github.com:acme/api \
  --git-key ~/.ssh/id_ed25519 \
  --port 3000

Self-hosted GitLab with custom CA

If your GitLab instance uses a self-signed or internal TLS certificate:

kip app deploy --name api \
  --git https://git.example.com/org/api \
  --git-token gldt-xxx \
  --git-ca-cert /path/to/ca.crt \
  --port 3000

The CA certificate is stored as a Kubernetes ConfigMap and mounted into the build pod automatically.

Planned providers

These are planned for future releases and are good first contributions:

• Gitea
• Forgejo
• Bitbucket

All providers implement the same GitProvider interface, making new providers a contained addition.

INFO

Git-based deployments (clone, build, deploy) are coming in Stage 2. The MVP supports image-based deployments only. The Git provider interface and URL detection are already implemented.