Provider Management¶

This page covers managing Crossplane providers in kindplane.

Configuration¶

Providers are configured in the crossplane.providers section:

crossplane:
  providers:
    - name: provider-aws
      package: xpkg.upbound.io/upbound/provider-aws:v1.1.0
    - name: provider-kubernetes
      package: xpkg.upbound.io/crossplane-contrib/provider-kubernetes:v0.12.0

Adding Providers After Bootstrap¶

Use the provider add command to add providers to a running cluster:

kindplane provider add provider-azure xpkg.upbound.io/upbound/provider-azure:v1.0.0

Listing Providers¶

List all installed providers:

kindplane provider list

Or using kubectl:

kubectl get providers

Provider Configuration¶

Most providers need a ProviderConfig to work with cloud resources. See the Credentials section for details.

AWS Provider¶

apiVersion: aws.upbound.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: aws-credentials
      key: credentials

Azure Provider¶

apiVersion: azure.upbound.io/v1beta1
kind: ProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: Secret
    secretRef:
      namespace: crossplane-system
      name: azure-credentials
      key: credentials

Kubernetes Provider¶

apiVersion: kubernetes.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
  name: default
spec:
  credentials:
    source: InjectedIdentity

Popular Providers¶

AWS Providers¶

Azure Providers¶

GCP Providers¶

Utility Providers¶

Troubleshooting Providers¶

Provider Not Healthy¶

Check provider status:

kubectl get providers -o wide
kubectl describe provider <provider-name>

View Provider Logs¶

kubectl logs -n crossplane-system -l pkg.crossplane.io/provider=<provider-name>

Common Issues¶

1. Package not found - Verify the package URL is correct
2. Missing credentials - Configure ProviderConfig with credentials
3. Resource limits - Increase Docker resource allocation