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 localtesting environments and Google Cloud environments.
Test containerized applications locally
To test your containerized application on your local workstation, you canconfigure your container to authenticate with yourlocal ADC file. For more information, seeConfigure ADC with your Google Account.
To test your implementation, use a local Kubernetes implementation such asminikube and thegcp-auth addon.
Run containerized applications on Google Cloud
You set up authentication for Google Cloud containerized environmentsdifferently depending on the environment:
- For Cloud Run, see call Google Cloud APIs with the service identity.
- For GKE, see Access Google Cloud APIs from GKE workloads.
- For GKE Enterprise, see theauthentication overview and Use fleet Workload Identity Federation for GKE.
- For Knative serving, see Using Workload Identity Federation for GKE for Knative serving.
What's next
- Learn more abouthow ADC finds credentials.
- Authenticate for using Cloud Client Libraries.
- Authenticate for using REST.
- Exploreauthentication methods.
Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2025-12-15 UTC.