Nodepools can't created anymore

[exocode]

Try to apply the /examples/cluster

It seems there is a "Version drift" between the crossplane and the Civo Kubernetes version (or something similar. Firewalls gets created, but clusters wont anymore.

I tried to reapply my (already working) manifests, and stuck at this error: (never saw that before):

CannotCreateExternalResource DatabaseKubernetesClusterInvalidVersionError: The Kubernetes cluster could not be created with a Civo deprecated k3s version

My Crosplane Providers, config etc. are the ones from the examples.
Did Civo changed something?

The only thing I did differently was using a manifest instead of kubectl crossplane install provider crossplane/provider-civo:main

my manifest

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: provider-civo
  annotations:
    argocd.argoproj.io/sync-wave: "-46"
spec:
  package: "crossplane/provider-civo:main"

[Igor992]

Just to add here that I'm facing the same issue from yesterday.
Following this guide - https://www.civo.com/learn/civo-crossplane-provider

This is what I use locally to reproduce it and it fails no matter if I use manifest or kubectl for install of the provider.

kubectl version --short
Client Version: v1.22.4
Server Version: v1.21.1

kubectl-crossplane --version
v1.6.1

kind version
kind v0.11.1 go1.17.2 darwin/amd64

[tbots]

unfortunately the same issue with creating cluster via crossplane, I have followed the guide https://www.civo.com/learn/civo-crossplane-provider

steps to repro:

• install cluster.yaml example
• kubectl apply -f cluster-test.yaml
• check for status: kubectl describe civokubernetes

status:

Status:
  At Provider:
  Conditions:
    Last Transition Time:  2022-01-19T16:52:25Z
    Reason:                Creating
    Status:                False
    Type:                  Ready
    Last Transition Time:  2022-01-19T16:52:29Z
    Message:               create failed: DatabaseKubernetesClusterInvalidVersionError: The Kubernetes cluster could not be created with a Civo deprecated k3s version
    Reason:                ReconcileError
    Status:                False
    Type:                  Synced

[RealHarshThakur]

@tbots @exocode @Igor992 The above PR should've fixed the issue.

[Igor992]

@RealHarshThakur,
thanks for patching this node pool issue.

But I'm not sure now if this is something at my side or at apiKey code side?

This is situation at the moment:

I checked this apiKey and it is fine at k8s secret side when I decrypt it from the SealedSecret controller.
Here is the apiKey from the cluster, I will regenerate a new one after this post.

I tried also to skip this controller and it is the same output scenario.

Thanks for checking this!

[RealHarshThakur]

I am not sure about this. Can you try recreating(delete and create) the secret and restarting the controller?
In any case, can you create another issue for this so we can discuss more on it?

[Igor992]

I tried that two times and the scenario was the same. I'll open a new issue about this.