Set up ADC for a containerized development environment
Stay organized with collections
Save and categorize content based on your preferences.
Authentication for containerized applications running on Cloud Run,
Google Kubernetes Engine, or GKE Enterprise is handled differently between local
testing environments and Google Cloud environments.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-20 UTC."],[[["\u003cp\u003eAuthentication for containerized applications differs between local testing and Google Cloud environments.\u003c/p\u003e\n"],["\u003cp\u003eLocal testing uses a local Application Default Credentials (ADC) file, configurable via a Google Account.\u003c/p\u003e\n"],["\u003cp\u003eLocal Kubernetes implementations like \u003ccode\u003eminikube\u003c/code\u003e with the \u003ccode\u003egcp-auth\u003c/code\u003e addon are recommended for testing.\u003c/p\u003e\n"],["\u003cp\u003eAuthentication setup in Google Cloud varies based on the environment, including GKE Enterprise, GKE, and Knative serving.\u003c/p\u003e\n"],["\u003cp\u003eWorkload Identity federation should be used for GKE and Knative serving.\u003c/p\u003e\n"]]],[],null,[]]
