Deployment rollout of a webapp in an unmanaged (on-premises) K8s cluster gets stuck.

spavez Registered Posts: 2 ✭✭✭

While deploying a webapp on an unmanaged K8s cluster, the pop up dialog never disappears saying:

Screen Shot 2021-08-17 at 16.43.25 PM.png

The pod starts and the application can be accessed without issues through a browser, but the Dataiku interface displays a 404 error:

Screen Shot 2021-08-17 at 16.44.52 PM.png

From the backend logs the following error appears:

[2021/08/17-19:43:01.650] [FT-WebAppBackendInstanceStartWaitThread-VRIm7lpq-167001] [INFO] [dku.webapps.dash] - [ct: 10510] No backend url ready[2021/08/17-19:43:01.650] [Thread-125678] [INFO] [dip.webapp.expose] - Get node IPs kubectl --namespace dssns-sergio-pavez-277091 get nodes -o json[2021/08/17-19:43:01.650] [Thread-125678] [INFO] [] - Starting process (regular)[2021/08/17-19:43:01.652] [Thread-125678] [INFO] [] - Process started with pid=16640[2021/08/17-19:43:01.767] [Thread-125678] [INFO] [dip.expose.endpoint.collector] - Register a backend {"expositionType":"node_port","id":"","scheme":"http","host":"","port":30650,"availability":"CLUSTER"}[2021/08/17-19:43:01.767] [Thread-125678] [ERROR] [dip.webapp.exposition.thread] - Failed to wait for exposition startjava.lang.NullPointerExceptionat com.dataiku.dip.webapps.backend.WebAppBackend.rewriteRedirectLine( com.dataiku.dip.webapps.backend.WebAppBackend.buildPublicNGINXConfig( com.dataiku.dip.webapps.backend.WebAppBackend.getPublicNGINXConfig( com.dataiku.dip.webapps.backend.WebAppBackend.writeNewNGINXConfig( com.dataiku.dip.webapps.backend.WebAppBackend.endpointsChanged( com.dataiku.dip.exposition.AbstractExposedEndpointCollector.registerPort( com.dataiku.dip.exposition.NodePortExposition$NodePortExpositionHandler.waitReady([2021/08/17-19:43:01.779] [process-resource-monitor-7069-165718] [DEBUG] [dku.resource] - Process stats for pid 7069: {"pid":7069,"commandName":"/home/dataiku/dss_design/code-envs/python/ds36/bin/python","cpuUserTimeMS":3050,"cpuSystemTimeMS":860,"cpuChildrenUserTimeMS":0,"cpuChildrenSystemTimeMS":10,"cpuTotalMS":3920,"cpuCurrent":0.0,"vmSizeMB":1669,"vmRSSMB":178,"vmHWMMB":253,"vmRSSAnonMB":163,"vmDataMB":1216,"vmSizePeakMB":1745,"vmRSSPeakMB":187,"vmRSSTotalMBS":303340,"majorFaults":0,"childrenMajorFaults":0}

If I try to run the application without K8s, it starts correctly and can be displayed on Dataiku. Attached is the full log of its execution.


  • Clément_Stenac
    Clément_Stenac Dataiker, Dataiku DSS Core Designer Posts: 753 Dataiker


    We strongly recommend keeping the default "port-forward" exposition mode for webapps, which provides all necessary capabilities without all of the deployment complexities associated with other modes, especially on a non-cloud environment.

    If this does not help, please open a support ticket ( and attach an instance diagnosis.


  • Ignacio_Toledo
    Ignacio_Toledo Dataiku DSS Core Designer, Dataiku DSS Core Concepts, Neuron 2020, Neuron, Registered, Dataiku Frontrunner Awards 2021 Finalist, Neuron 2021, Neuron 2022, Frontrunner 2022 Finalist, Frontrunner 2022 Winner, Dataiku Frontrunner Awards 2021 Participant, Frontrunner 2022 Participant, Neuron 2023 Posts: 411 Neuron

    Hi @Clément_Stenac

    Thanks for the quick reply. With @spavez
    we are using the "port-forward" exposition mode indeed.

    Following your suggestion, we will open a support ticket to further investigate the problem.


Setup Info
      Help me…