kindplane credentials¶
Configure cloud provider credentials for Crossplane.
Usage¶
Subcommands¶
| Command | Description |
|---|---|
configure | Interactive credential setup |
kindplane credentials configure¶

Interactively configure credentials for cloud providers.
Usage¶
Description¶
The configure command guides you through setting up credentials for each Crossplane provider in your cluster.
Interactive Flow¶
╭────────────────────────────────────────────────────────────────╮
│ Credential Configuration │
╰────────────────────────────────────────────────────────────────╯
Select provider to configure:
1. AWS
2. Azure
3. Kubernetes
4. Exit
> 1
AWS Credential Configuration
─────────────────────────────
Select credential source:
1. Environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY)
2. AWS CLI profile
3. Credentials file
4. Skip
> 2
Enter AWS profile name [default]: development
✓ AWS credentials configured
Profile: development
Secret: aws-credentials (crossplane-system)
ProviderConfig: default
What Gets Created¶
Secrets¶
Credentials are stored as Kubernetes secrets:
| Secret | Provider |
|---|---|
aws-credentials | AWS |
azure-credentials | Azure |
ProviderConfigs¶
ProviderConfig resources are created to reference the secrets:
Manual Configuration¶
You can also configure credentials manually:
AWS¶
-
Create the secret:
-
Create ProviderConfig:
Azure¶
-
Create the secret:
-
Create ProviderConfig:
Kubernetes (In-Cluster)¶
apiVersion: kubernetes.crossplane.io/v1alpha1
kind: ProviderConfig
metadata:
name: default
spec:
credentials:
source: InjectedIdentity
Verifying Credentials¶
After configuration, verify providers are healthy:
Or:
If a provider shows Unhealthy, check the provider logs:
Security Notes¶
Local Development Only
The credential storage method used by kindplane is suitable for local development only. For production:
- Use IRSA (AWS)
- Use Workload Identity (Azure/GCP)
- Use External Secrets Operator
- Use Vault