fix: adk deploy docker file file permission

[moficodes]

Currently in adk deploy cloud_run or gke, the dockerfile copies the agent code after the file permission is set. This can lead to file permission not being set correctly for the container to open and read the file.

This PR will make sure the files are copied with the permission of the user that is set in the container.

[adk-bot]

Response from ADK Triaging Agent

Hello @moficodes, thank you for creating this PR!

This PR is a bug fix, could you please associate the github issue with this PR? If there is no existing issue, could you please create one?

In addition, could you please include a testing plan section in your PR to talk about how you will test and provide logs or screenshot after the fix is applied?

This information will help reviewers to review your PR more efficiently. Thanks!

[moficodes]

@hangfei

[hangfei]

Response from ADK Triaging Agent

Hello @moficodes, thank you for creating this PR!

This PR is a bug fix, could you please associate the github issue with this PR? If there is no existing issue, could you please create one?

In addition, could you please include a testing plan section in your PR to talk about how you will test and provide logs or screenshot after the fix is applied?

This information will help reviewers to review your PR more efficiently. Thanks!

@moficodes could you provide your testing plan?

[hangfei]

Please also provide an instruction on how to test this.

[vicentefb]

The way to test the command out would be through the new adk command like the following:

adk deploy gke --project GKE_PROJECT_ID --cluster_name CLUSTER_NAME --region REGION --with_ui path/to/agent.py/folder/

This is going to create a Deployment and Service K8s resources that you will see in your cluster and then a pod will be running.

Verify the deployment using kubectl:

1. Check the Pods: Ensure your agent's pods are in the Running state.

kubectl get pods

You should see output like adk-default-service-name-xxxx-xxxx ... 1/1 Running in the default namespace.

2. Find the External IP: Get the public IP address for your agent's service.

kubectl get service
NAME                       TYPE           CLUSTER-IP      EXTERNAL-IP     PORT(S)        AGE
adk-default-service-name   LoadBalancer   34.118.228.70   34.63.153.253   80:32581/TCP   5d20h

Navigate to the EXTERNAL-IP and interact with your agent via the UI.

[moficodes]

/retest

[moficodes]

@hangfei

Could you run the test again?

[DeanChensj]

Hi @moficodes I just triggered the flow, it seems that you need to run the autoformat.sh in the repo to format your change.

[moficodes]

Formatted.

One more test run. :)

[DeanChensj]

merged in ad81aa5

Thanks @moficodes and @vicentefb for the help!