Kubernetes 버전 1.22에서 Kubernetes 프로젝트에서는 kubectl 명령줄 도구와 같이 Kubernetes API 서버에 액세스하기 위해 클라이언트에서 사용되는 기본 제공되는 인증 메커니즘이 사용 중단되었습니다. 기본 제공되는 인증 메커니즘은 Kubernetes 1.26에서 제거될 예정입니다. 관련 정보는 GitHub PR 102181을 참조하세요.
삭제는 클러스터에 배포되고 Kubernetes 서비스 계정을 사용하여 API 서버와 통신하는 연산자에게 영향을 주지 않습니다.
어떻게 해야 할까요?
GKE에서 업데이트된 인증 플러그인 gke-gcloud-auth-plugin이 출시되었습니다. 이 플러그인은 client-go Credential Plugins 프레임워크를 사용하여 GKE 클러스터와 통신하기 위한 인증 토큰을 제공합니다.
명령줄 클라이언트를 버전 1.26 이상으로 업데이트하기 전 이 플러그인을 설치해야 합니다. 플러그인을 설치하지 않으면 다음과 비슷한 오류 메시지가 표시됩니다.
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found
panic: no Auth Provider found for name gcp
오류 예시: 실행 가능한 gke-cloud-auth-plugin을 찾을 수 없음
Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found
It looks like you are trying to use a client-go credential plugin that is not installed.
To learn more about this feature, consult the documentation available at:
https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins
Install gke-gcloud-auth-plugin for use with kubectl by following \
https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Deprecated authentication plugin for Kubernetes clients\n\n*** ** * ** ***\n\nIn Kubernetes version 1.22, the Kubernetes project deprecated the built-in\nauthentication mechanism used by clients such as the `kubectl` command-line tool\nto access the Kubernetes API server. The built-in authentication mechanism is\nscheduled for removal in Kubernetes 1.26. For context, refer to\n[GitHub PR 102181](https://github.com/kubernetes/kubernetes/pull/102181).\n\nThe removal doesn't affect operators that are deployed in the cluster and use\nKubernetes service accounts to communicate with the API server.\n\nWhat should you do?\n-------------------\n\nGKE released an updated authentication plugin,\n`gke-gcloud-auth-plugin`. This plugin uses the\n[client-go Credential Plugins](https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins)\nframework to provide authentication tokens to communicate with\nGKE clusters.\n\nYou must install the plugin before you update your command-line clients\nto version 1.26 and later. If you don't install the plugin, you'll notice an\nerror message similar to the following.\n\nFor instructions, refer to\n[Install required plugins](/kubernetes-engine/docs/how-to/cluster-access-for-kubectl#install_plugin).\n\n### Example error: No auth provider found\n\n Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found\n\n panic: no Auth Provider found for name gcp\n\n### Example error: Executable gke-cloud-auth-plugin not found\n\n Unable to connect to the server: getting credentials: exec: executable gke-gcloud-auth-plugin not found\n\n It looks like you are trying to use a client-go credential plugin that is not installed.\n\n To learn more about this feature, consult the documentation available at:\n https://kubernetes.io/docs/reference/access-authn-authz/authentication/#client-go-credential-plugins\n\n Install gke-gcloud-auth-plugin for use with kubectl by following \\\n https://cloud.google.com/blog/products/containers-kubernetes/kubectl-auth-changes-in-gke."]]
