[[["이해하기 쉬움","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-08-18(UTC)"],[[["\u003cp\u003eThis content details the creation of the \u003ccode\u003eapigee\u003c/code\u003e Kubernetes namespace, which is where Apigee hybrid components will be deployed and run.\u003c/p\u003e\n"],["\u003cp\u003eThe namespace specified in the \u003ccode\u003eoverrides.yaml\u003c/code\u003e file will be used, with \u003ccode\u003eapigee\u003c/code\u003e being the default if no other namespace is given.\u003c/p\u003e\n"],["\u003cp\u003eTo verify if the namespace exists, the command \u003ccode\u003ekubectl get namespace APIGEE_NAMESPACE\u003c/code\u003e is used.\u003c/p\u003e\n"],["\u003cp\u003eIf the \u003ccode\u003eapigee\u003c/code\u003e namespace does not exist, it can be created using \u003ccode\u003ekubectl create namespace APIGEE_NAMESPACE\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eAfter creating the namespace, the subsequent step is to set up the necessary Google Cloud service accounts and credentials for the hybrid runtime components.\u003c/p\u003e\n"]]],[],null,[]]
