Kubernetes Gitlab

Deploys a GitLab instance on Kubernetes with a ClusterIP Service, optional namespace creation, configurable container resources, and optional Ingress with TLS termination via cert-manager and Istio.

What Gets Created

When you deploy a KubernetesGitlab resource, OpenMCF provisions:

• Namespace — created only when createNamespace is true
• ClusterIP Service — exposes GitLab on port 80 (targeting container port 8080) with app-level selectors derived from the resource metadata
• Ingress — created only when ingress.enabled is true, routes HTTPS traffic to the Service using the Istio ingress class with automatic TLS certificates from cert-manager (letsencrypt-prod issuer)

Prerequisites

• Kubernetes credentials configured via environment variables or OpenMCF provider config
• A Kubernetes namespace that already exists, or set createNamespace to true
• Istio installed in the cluster if enabling ingress (the Ingress uses ingressClassName: istio)
• cert-manager with a letsencrypt-prod ClusterIssuer if enabling ingress with TLS

Quick Start

Create a file gitlab.yaml:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesGitlab
metadata:
  name: my-gitlab
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesGitlab.my-gitlab
spec:
  namespace: gitlab
  createNamespace: true
  container:
    resources:
      limits:
        cpu: "1000m"
        memory: "1Gi"
      requests:
        cpu: "50m"
        memory: "100Mi"

Deploy:

openmcf apply -f gitlab.yaml

This creates a GitLab instance in the gitlab namespace with a ClusterIP Service on port 80, using the default resource limits.

Configuration Reference

Required Fields

Optional Fields

Examples

Development GitLab with Minimal Resources

A lightweight GitLab instance for development with reduced CPU and memory:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesGitlab
metadata:
  name: dev-gitlab
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: dev.KubernetesGitlab.dev-gitlab
spec:
  namespace: dev
  createNamespace: true
  container:
    resources:
      limits:
        cpu: "500m"
        memory: "512Mi"
      requests:
        cpu: "50m"
        memory: "128Mi"

Production GitLab with Ingress

A production GitLab instance with higher resource limits and HTTPS ingress:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesGitlab
metadata:
  name: prod-gitlab
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: prod.KubernetesGitlab.prod-gitlab
spec:
  namespace: production
  container:
    resources:
      limits:
        cpu: "4000m"
        memory: "8Gi"
      requests:
        cpu: "1000m"
        memory: "2Gi"
  ingress:
    enabled: true
    hostname: gitlab.example.com

Using Foreign Key References

Reference an OpenMCF-managed namespace instead of hardcoding the name:

apiVersion: kubernetes.openmcf.org/v1
kind: KubernetesGitlab
metadata:
  name: team-gitlab
  labels:
    openmcf.org/provisioner: pulumi
    pulumi.openmcf.org/organization: my-org
    pulumi.openmcf.org/project: my-project
    pulumi.openmcf.org/stack.name: staging.KubernetesGitlab.team-gitlab
spec:
  namespace:
    valueFrom:
      kind: KubernetesNamespace
      name: platform-ns
      field: spec.name
  container:
    resources:
      limits:
        cpu: "2000m"
        memory: "4Gi"
      requests:
        cpu: "500m"
        memory: "1Gi"
  ingress:
    enabled: true
    hostname: gitlab.staging.example.com

Note: The namespace field accepts either a plain string value or a valueFrom reference to another resource. When using valueFrom, the value is resolved at deployment time from the referenced resource's field.

Stack Outputs

After deployment, the following outputs are available in status.outputs:

Related Components

• KubernetesNamespace — provides the target namespace via valueFrom reference
• KubernetesDeployment — application deployments that integrate with GitLab
• KubernetesRedis — Redis cache commonly used alongside GitLab for session storage and caching
• KubernetesPostgres — PostgreSQL database used by GitLab as its primary data store