Tarik-Kada commented on issue #5475:
URL: https://github.com/apache/openwhisk/issues/5475#issuecomment-2049176715

   I run into the same problem when trying to deploy with Kubernetes in Docker.
   
   When I try to deploy a local build to some of the pods, they keep crashing 
and will not initialize. Here is an example using the controller component:
   `[2024-04-09T14:12:48.516Z] [INFO] [#tid_sid_controller] [Controller] 
starting controller instance 0 [marker:controller_startup0_counter:604]
   [2024-04-09T14:12:48.816Z] [INFO] [#tid_sid_dispatcher] [MessageFeed] 
handler capacity = 128, pipeline fill at = 128, pipeline depth = 256
   Exception in thread "main" pureconfig.error.ConfigReaderException: Cannot 
convert configuration to a org.apache.openwhisk.core.etcd.EtcdConfig. Failures 
are:
     at 'whisk':
       - Key not found: 'etcd'.
   
           at pureconfig.package$.getResultOrThrow(package.scala:139)
           at pureconfig.package$.loadConfigOrThrow(package.scala:161)
           at 
org.apache.openwhisk.core.loadBalancer.FPCPoolBalancer$.instance(FPCPoolBalancer.scala:721)
           at 
org.apache.openwhisk.core.controller.Controller.<init>(Controller.scala:119)
           at 
org.apache.openwhisk.core.controller.Controller$.start(Controller.scala:338)
           at 
org.apache.openwhisk.core.controller.Controller$.main(Controller.scala:291)
           at 
org.apache.openwhisk.core.controller.Controller.main(Controller.scala)`
   
   However, when I deploy openWhisk through:
   `helm install owdev openwhisk/openwhisk -n openwhisk --create-namespace`, 
Everything initializes nicely and I can create and invoke functions.
   
   I want to use OpenWhisk for my research project, but this is making it hard 
to start developing.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to