Troubleshooting Crossplane provider-gcp-dns installation after uninstalling Crossplane

[Marc Cortinas Val]

Hi everyone,

I'm facing an issue with installing the Crossplane provider-gcp-dns in my GKE environment after completely uninstalling Crossplane. I have an automated setup (argocd reconciling via helm) that installs Crossplane, the providerconfig, and the provider-gcp-dns in three GKE clusters.

Problem: When I uninstall Crossplane and try to reinstall the provider-gcp-dns, the installation of the "upbound-provider-family-gcp" family doesn't start. I've priously deleted all the provider, providerrevisions, deploymentruntimeconfig, and providers objects in the uninstallation phase, but the issue persists when I try to install after that.

Error message: Upon reinstallation, the provider-gcp-dns complains with the error "provider: error: cannot create default store config: no matches for kind "StoreConfig" in version "gcp.upbound.io/v1alpha1"".

Steps taken: I've tried manually applying the following manifest to create the "upbound-provider-family-gcp" provider:

YAML

apiVersion: pkg.crossplane.io/v1
kind: Provider
metadata:
  name: upbound-provider-family-gcp
spec:
  ignoreCrossplaneConstraints: false
  package: xpkg.upbound.io/upbound/provider-family-gcp:v1.10.0
  packagePullPolicy: IfNotPresent
  revisionActivationPolicy: Automatic
  revisionHistoryLimit: 1
  runtimeConfigRef:
    apiVersion: pkg.crossplane.io/v1beta1
    kind: DeploymentRuntimeConfig
    name: default
  skipDependencyResolution: false

This seems to partially resolve the issue, but the underlying problem persists.

Environment:

• Crossplane version: 1.18
• Kubernetes version: v1.30.5-gke.1443001 | v1.31.1-gke.1678000
• GCP provider version: 1.10.0

Questions:

• Am I missing any steps during the uninstallation or reinstallation process?
• Could there be any lingering configuration or state causing this issue?
• Is there a specific troubleshooting guide or best practice for this scenario?

Any help or insights would be greatly appreciated. 

Thanks in advance!

[Marc Cortinas]

Great news! I finally found a simple workaround. This involves removing the object lock.locks.pkg.crossplane.io. After removing all the CRDs (Custom Resource Definitions) and this object today, I'm happy to report that everything is working again in the previously created GKE clusters!