Files
Sankofa/crossplane-provider-proxmox/examples/provider-config-template.yaml
defiQUG 4880a9d6c3
Some checks failed
CD Pipeline / Deploy to Staging (push) Has been cancelled
CD Pipeline / Deploy to Production (push) Has been cancelled
CI Pipeline / Lint and Type Check (push) Has been cancelled
CI Pipeline / Test Backend (push) Has been cancelled
CI Pipeline / Test Frontend (push) Has been cancelled
CI Pipeline / Build (push) Has been cancelled
CI Pipeline / Security Scan (push) Has been cancelled
Deploy to Staging / Deploy to Staging (push) Has been cancelled
Test Suite / frontend-tests (push) Has been cancelled
Test Suite / api-tests (push) Has been cancelled
Test Suite / blockchain-tests (push) Has been cancelled
Type Check / type-check (map[directory:. name:root]) (push) Has been cancelled
Type Check / type-check (map[directory:api name:api]) (push) Has been cancelled
Type Check / type-check (map[directory:portal name:portal]) (push) Has been cancelled
Build Crossplane Provider / build (push) Has been cancelled
Crossplane Provider CI / Go Test (push) Has been cancelled
Crossplane Provider CI / Go Lint (push) Has been cancelled
Crossplane Provider CI / Go Build (push) Has been cancelled
Validate Configuration Files / validate (push) Has been cancelled
Update Proxmox provider configuration examples for improved clarity and security
- Revised provider-config-template.yaml and provider-config.yaml to reflect updated site names and endpoints for better alignment with VM specifications.
- Enhanced documentation regarding authentication methods, emphasizing the use of token-based authentication for production environments.
- Updated namespace references to ensure consistency across configuration files.
2025-12-13 05:10:55 -08:00

48 lines
1.5 KiB
YAML

apiVersion: proxmox.sankofa.nexus/v1alpha1
kind: ProviderConfig
metadata:
name: proxmox-provider-config
namespace: crossplane-system
spec:
credentials:
source: Secret
secretRef:
namespace: crossplane-system
name: proxmox-credentials
# Note: The 'key' field is optional and ignored by the controller.
# The controller reads 'username' and 'password' keys from the secret.
# For token-based auth, use 'token' and 'tokenid' keys instead.
sites:
# Site names must match the 'site' field in VM specifications
# VM specs use 'site-1' and 'site-2', so these names must match exactly
- name: site-1
endpoint: "https://192.168.11.10:8006"
# Alternative: "https://ml110-01.sankofa.nexus:8006" (if DNS configured)
node: "ml110-01"
insecureSkipTLSVerify: true
- name: site-2
endpoint: "https://192.168.11.11:8006"
# Alternative: "https://r630-01.sankofa.nexus:8006" (if DNS configured)
node: "r630-01"
insecureSkipTLSVerify: true
---
# Secret template - DO NOT COMMIT WITH REAL CREDENTIALS
apiVersion: v1
kind: Secret
metadata:
name: proxmox-credentials
namespace: crossplane-system
type: Opaque
stringData:
# Option 1: Username/Password authentication
username: "root@pam"
password: "CHANGE_ME"
# Option 2: Token-based authentication (recommended for production)
# tokenid: "root@pam!api-token-name"
# token: "your-api-token-secret"
# WARNING: Replace with your actual credentials!
# Do not commit real passwords or tokens to version control.