# Unable to deploy Multiple functions when handler function is inside other folder in minikube regarding kubeless

**URL:** <https://forum.serverless.com/t/unable-to-deploy-multiple-functions-when-handler-function-is-inside-other-folder-in-minikube-regarding-kubeless/6862>\
**Category:** Serverless Framework\
**Created:** [January 2, 2019, 7:37am UTC](https://forum.serverless.com/t/unable-to-deploy-multiple-functions-when-handler-function-is-inside-other-folder-in-minikube-regarding-kubeless/6862 "2019-01-02T07:37:17Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![maneet8](https://avatars.discourse-cdn.com/v4/letter/m/c2a13f/32.png) [@maneet8](https://forum.serverless.com/u/maneet8)\
**Post date:** [January 2, 2019, 7:37am UTC](https://forum.serverless.com/t/unable-to-deploy-multiple-functions-when-handler-function-is-inside-other-folder-in-minikube-regarding-kubeless/6862/1 "2019-01-02T07:37:17Z")

</div>

I am unable to deploy multiple functions when handler function is inside other folder.  
Clone the below project, which I have picked up from these examples only and slightly modified the folder structure.

> **[GitHub - maneet8/testserverlesskubeless: I have picked up this example for...](https://github.com/maneet8/testserverlesskubeless)**
>
> I have picked up this example for raising issue on serverless-kubeless regarding multiple functions deployment on minikube - GitHub - maneet8/testserverlesskubeless: I have picked up this example f...

Run npm install

Run serverless deploy

I am getting below error on deployment

$ serverless deploy -v  
Serverless: Packaging service…  
Serverless: Excluding development dependencies…  
Serverless: Unable to find any running pod for read-all. Retrying…  
Serverless: Unable to find any running pod for create. Retrying…  
Serverless: Unable to find any running pod for read-one. Retrying…  
Serverless: Unable to find any running pod for update. Retrying…  
Serverless: Unable to find any running pod for delete. Retrying…  
Serverless: Unable to find any running pod for delete. Retrying…  
Serverless: Unable to find any running pod for create. Retrying…  
Serverless: Unable to find any running pod for read-one. Retrying…  
Serverless: Unable to find any running pod for update. Retrying…  
Serverless: Unable to find any running pod for read-all. Retrying…  
Serverless: Unable to find any running pod for delete. Retrying…  
Serverless: Unable to find any running pod for read-all. Retrying…  
Serverless: Unable to find any running pod for update. Retrying…  
Serverless: Unable to find any running pod for read-one. Retrying…  
Serverless: Unable to find any running pod for create. Retrying…  
Serverless: Unable to find any running pod for read-all. Retrying…  
Serverless: Unable to find any running pod for update. Retrying…  
Serverless: Unable to find any running pod for read-one. Retrying…  
Serverless: Unable to find any running pod for create. Retrying…  
Serverless: Unable to find any running pod for delete. Retrying…  
Serverless: Giving up, unable to retrieve the status of the read-one deployment.  
Serverless: Giving up, unable to retrieve the status of the read-all deployment.

C:\Users\maneet\AppData\Roaming\npm\node\_modules\serverless\lib\classes\Error.js:92  
throw new Error(e);  
^  
Error: Unable to retrieve the status of the read-one deployment  
at module.exports.logError (C:\Users\maneet\AppData\Roaming\npm\node\_modules\serverless\lib\classes\Error.js:92:11)  
at process.on (C:\Users\maneet\AppData\Roaming\npm\node\_modules\serverless\bin\serverless:22:3)  
at emitTwo (events.js:126:13)  
at process.emit (events.js:214:7)  
at process.emit (C:\Users\maneet\AppData\Roaming\npm\node\_modules\serverless\node\_modules\source-map-support\source-map-support.js:461:21)  
at methodName (D:\workdir\testserverlesskubeless\node\_modules\bluebird\js\release\debuggability.js:199:33)  
at activeFireEvent (D:\workdir\testserverlesskubeless\node\_modules\bluebird\js\release\debuggability.js:242:44)  
at fireRejectionEvent (D:\workdir\testserverlesskubeless\node\_modules\bluebird\js\release\debuggability.js:632:14)  
at Promise.\_notifyUnhandledRejection (D:\workdir\testserverlesskubeless\node\_modules\bluebird\js\release\debuggability.js:65:9)  
at Timeout.\_onTimeout (D:\workdir\testserverlesskubeless\node\_modules\bluebird\js\release\debuggability.js:44:14)  
at ontimeout (timers.js:498:11)  
at tryOnTimeout (timers.js:323:5)  
at Timer.listOnTimeout (timers.js:290:5)

With the same folder structure I am able to deploy on AWS Lambda.