[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2024-12-21(UTC)"],[[["\u003cp\u003eThis guide outlines the process for installing, upgrading, and uninstalling v1alpha1 Custom Resource Definitions (CRDs) for Google Cloud resources within Config Connector.\u003c/p\u003e\n"],["\u003cp\u003ev1alpha1 CRDs are not managed by the Config Connector operator or add-on, therefore, they require manual upgrades when the Config Connector version is upgraded to maintain functionality.\u003c/p\u003e\n"],["\u003cp\u003eInstallation and upgrading of specific or all v1alpha1 CRDs involves cloning the Config Connector GitHub repository, checking out the correct version, and using \u003ccode\u003ekubectl apply\u003c/code\u003e commands.\u003c/p\u003e\n"],["\u003cp\u003eUninstalling v1alpha1 CRDs requires deleting any associated CRs, checking out the appropriate Config Connector version, and executing \u003ccode\u003ekubectl delete\u003c/code\u003e commands.\u003c/p\u003e\n"],["\u003cp\u003eUninstalling the v1alpha1 CRDs will abandon the CRs, but the corresponding Google Cloud resources will still remain.\u003c/p\u003e\n"]]],[],null,["# Installing Config Connector v1alpha1 CRDs\n=========================================\n\n*** ** * ** ***\n\nThis topic explains how to install v1alpha1 Google Cloud resource [Custom\nResource\nDefinitions](https://kubernetes.io/docs/concepts/extend-kubernetes/api-extension/custom-resources/)\n(CRDs) in Config Connector.\n| **Warning:** Config Connector v1alpha1 Google Cloud resource CRDs should not be used in production. When Config Connector is upgraded, the v1alpha1 CRDs must be manually upgraded to ensure they continue to work. You must manually install, upgrade, and uninstall the v1alpha1 CRDs, as they are not managed by the Config Connector operator or the Config Connector add-on.\n\nBefore you begin\n----------------\n\n1. Ensure Config Connector is\n [installed manually](/config-connector/docs/how-to/install-manually) or through the\n [GKE add-on](/config-connector/docs/how-to/install-upgrade-uninstall).\n\n2. Check your Config Connector version and ensure it is 1.103.0 and above. You\n can check the Config Connector version by connecting to the cluster where\n Config Connector is installed and running the following command:\n\n kubectl get ns cnrm-system -o jsonpath='{.metadata.annotations.cnrm\\.cloud\\.google\\.com/version}'\n\nInstalling the v1alpha1 CRDs\n----------------------------\n\n1. Clone the [GitHub\n repository](https://github.com/GoogleCloudPlatform/k8s-config-connector):\n\n git clone https://github.com/GoogleCloudPlatform/k8s-config-connector\n\n2. `git checkout` to your Config Connector version:\n\n cd k8s-config-connector\n echo 'v'$(kubectl get ns cnrm-system -o jsonpath='{.metadata.annotations.cnrm\\.cloud\\.google\\.com/version}') | xargs git checkout\n\n3. Install the v1alpha1 CRDs:\n\n cd crds\n\n 1. If you want to install a specific v1alpha1 CRD, run the following\n command:\n\n kubectl apply -f \u003cvar translate=\"no\"\u003eCRD_FILENAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003eCRD_FILENAME\u003c/var\u003e with the filename of the\n v1alpha1 CRD you want to install.\n 2. If you want to install all the v1alpha1 CRDs, run the following command:\n\n kubectl apply $(ls *v1alpha1*.yaml | awk ' { print \" -f \" $1 } ')\n\nThe v1alpha1 CRDs are successfully installed when the `kubectl apply` command\nsuccessfully completes.\n\nUpgrading the v1alpha1 CRDs\n---------------------------\n\n| **Warning:** The v1alpha1 CRDs need to be upgraded after your Config Connector version is upgraded to ensure the existing CRs of the v1alpha1 CRDs still work.\n| **Warning:** Downgrading the v1alpha1 CRDs is not supported.\n\n1. Ensure Config Connector version is upgraded before you upgrade the v1alpha1\n CRDs.\n\n2. `git checkout` to your Config Connector version at your local\n Config Connector repository:\n\n echo 'v'$(kubectl get ns cnrm-system -o jsonpath='{.metadata.annotations.cnrm\\.cloud\\.google\\.com/version}') | xargs git checkout\n\n3. Upgrade the v1alpha1 CRDs:\n\n cd crds\n\n 1. If you want to upgrade a specific v1alpha1 CRD, run the following\n command:\n\n kubectl apply -f \u003cvar translate=\"no\"\u003eCRD_FILENAME\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003eCRD_FILENAME\u003c/var\u003e with the filename of the\n v1alpha1 CRD you want to install.\n 2. If you want to upgrade all the v1alpha1 CRDs, run the following command:\n\n kubectl apply $(ls *v1alpha1*.yaml | awk ' { print \" -f \" $1 } ')\n\nThe v1alpha1 CRDs are successfully upgraded when the `kubectl apply` command\nsuccessfully completes.\n\nUninstalling the v1alpha1 CRDs\n------------------------------\n\n1. [Delete the CRs](/config-connector/docs/how-to/managing-deleting-resources)\n for v1alpha1 CRDs if you no longer need the underlying Google Cloud\n resources. Otherwise, skip this step.\n\n | **Note:** The CRs are [abandoned](/config-connector/docs/how-to/managing-deleting-resources#keeping_resources_after_deletion) when the v1alpha1 CRDs are uninstalled. The corresponding Google Cloud resources will still exist.\n2. Check out to your Config Connector version at your local Config Connector\n repository:\n\n echo 'v'$(kubectl get ns cnrm-system -o jsonpath='{.metadata.annotations.cnrm\\.cloud\\.google\\.com/version}') | xargs git checkout\n\n3. Uninstall the v1alpha1 CRDs:\n\n cd crds\n kubectl delete $(ls *v1alpha1*.yaml | awk ' { print \" -f \" $1 } ')\n\nThe v1alpha1 CRDs are successfully uninstalled if the `kubectl delete` command\nsuccessfully completes."]]