Skip to main content
Version: 0.3

Dynamic Provisioning Prerequisites

Complete these prerequisites before using dynamic environment provisioning with GitOps catalogs.

Required Catalogs​

Create at least one catalog before provisioning environments dynamically:

  • IAC Catalog (recommended): For provisioning infrastructure resources
  • YAML Catalog (recommended): For deploying platform tools and applications
  • Hybrid Catalog (optional): For combined infrastructure and application deployment

See the Catalog documentation to create your first catalogs.

Required Access​

  • Platform Admin or Team Admin role in Konstruct
  • Git repository access to your organization's GitOps repository
  • Cloud provider credentials configured in Crossplane (for IAC catalogs)

Required Infrastructure​

  • Target cluster provisioned and registered in Konstruct
  • Crossplane installed (for IAC catalog provisioning)
  • ArgoCD installed and configured
  • Secret backend configured (Vault, AWS Secrets Manager, or Azure Key Vault)

Understanding of Concepts​

Before using dynamic provisioning, understand:

Validation Steps​

1. Verify Catalog Availability​

  1. Navigate to Catalogs in Konstruct UI

  2. Confirm at least one catalog appears in the list

  3. Click a catalog to verify parameters display correctly

2. Check Cluster Configuration​

  1. Navigate to Clusters in Konstruct UI

  2. Verify target cluster shows Active status

  3. Confirm cluster has necessary resources (CPU, memory, storage)

3. Verify Crossplane (for IAC Catalogs)​

Check Crossplane is installed and configured:

kubectl get provider -n crossplane-system
kubectl get providerconfig -n crossplane-system

Expected output should show active providers.

4. Verify ArgoCD​

Check ArgoCD is installed and accessible:

kubectl get applications -n argocd

Optional: Test Catalog Deployment​

Before using dynamic provisioning, test catalog deployment manually:

  1. Deploy a YAML catalog to an environment

  2. Verify the catalog deploys successfully

  3. Check that resources appear in the cluster

This validates your catalogs work correctly before automating with dynamic provisioning.

What's Next?​