From 869a70713bb90ec72e26d9a6cfe40d2d43e1b311 Mon Sep 17 00:00:00 2001 From: Michael Kibbe Date: Wed, 8 May 2019 15:53:16 -0700 Subject: [PATCH] add comment about potential backwards-incompatibility of CRDs --- README.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/README.md b/README.md index d9d806ad7b..d21a53ac8c 100644 --- a/README.md +++ b/README.md @@ -57,6 +57,12 @@ For existing Kubernetes applications that are currently using additional tools ( ```bash kubectl apply -f install-bundle/ ``` + **NOTE:** If you previously installed Config Connector alpha and wish to + upgrade, newer versions of the `CustomResourceDefinitions` may cause some of + the resources to not be applied successfully. You will need to delete the + previous version of the CRD via `kubectl delete crd [NAME]`, and then rerun + the installation command above. *This will delete any resources of that + particular type*. 1. In order to create Google Cloud resources, Config Connector needs an IAM service account to authenticate as. Create a service account, create a key for the service account, and inject it in the cluster: