What happened?
i'm using the provider-civo provider (https://marketplace.upbound.io/providers/civo/provider-civo/v0.1) to spin up a new cluster on civo using crossplane. i'm completely stuck with the error: in the resultant civokubernetes resource.
Status:
At Provider:
Conditions:
Last Transition Time: 2024-08-21T15:52:31Z
Reason: Creating
Status: False
Type: Ready
Last Transition Time: 2024-08-21T15:52:34Z
Message: create failed: Error: Unknown error response - status: 409 Conflict, code: 409, reason: {"code":"database_duplicate_cluster_name_not_allowed","reason":"A cluster with this name already exists"}
But ofcourse there's no duplicate name that i can find when running. it worked up until about a day ago (i suspect it has something to do with civo deprecating v1.27.0)
How can we reproduce it?
use attached files and follow instructions;
helm upgrade --install crossplane crossplane-stable/crossplane --namespace crossplane-system --create-namespace --wait
echo "apiVersion: v1\nkind: Secret\nmetadata:\n name: civo-creds\ntype: Opaque\ndata:\n credentials: $CIVO_TOKEN_ENCODED" | kubectl --namespace crossplane-system apply --filename -
kubectl apply -f xrds.yaml
kubectl apply -f providers/civo.yaml
kubectl apply -f compositions.yaml
kubectl apply -f provider-configs/provider-config-civo.yaml
kubectl create ns infra
kubectl apply -f civo_claim.yaml
crossplane.zip
What environment did it happen in?
Crossplane version:
xpkg.upbound.io/crossplane/crossplane:v1.16.0
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.2
WARNING: version difference between client (1.30) and server (1.27) exceeds the supported minor version skew of +/-1
macos on an m1
Darwin Liquids-MacBook-Pro.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000 arm64
What happened?
i'm using the provider-civo provider (https://marketplace.upbound.io/providers/civo/provider-civo/v0.1) to spin up a new cluster on civo using crossplane. i'm completely stuck with the error: in the resultant civokubernetes resource.
Status:
At Provider:
Conditions:
Last Transition Time: 2024-08-21T15:52:31Z
Reason: Creating
Status: False
Type: Ready
Last Transition Time: 2024-08-21T15:52:34Z
Message: create failed: Error: Unknown error response - status: 409 Conflict, code: 409, reason: {"code":"database_duplicate_cluster_name_not_allowed","reason":"A cluster with this name already exists"}
But ofcourse there's no duplicate name that i can find when running. it worked up until about a day ago (i suspect it has something to do with civo deprecating v1.27.0)
How can we reproduce it?
use attached files and follow instructions;
helm upgrade --install crossplane crossplane-stable/crossplane --namespace crossplane-system --create-namespace --wait
echo "apiVersion: v1\nkind: Secret\nmetadata:\n name: civo-creds\ntype: Opaque\ndata:\n credentials: $CIVO_TOKEN_ENCODED" | kubectl --namespace crossplane-system apply --filename -
kubectl apply -f xrds.yaml
kubectl apply -f providers/civo.yaml
kubectl apply -f compositions.yaml
kubectl apply -f provider-configs/provider-config-civo.yaml
kubectl create ns infra
kubectl apply -f civo_claim.yaml
crossplane.zip
What environment did it happen in?
Crossplane version:
xpkg.upbound.io/crossplane/crossplane:v1.16.0
Client Version: v1.30.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.27.2
WARNING: version difference between client (1.30) and server (1.27) exceeds the supported minor version skew of +/-1
macos on an m1
Darwin Liquids-MacBook-Pro.local 22.4.0 Darwin Kernel Version 22.4.0: Mon Mar 6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000 arm64