![[17.0.0.3 and later]](../ng_v17003plus.gif)
Liberty Helm chart
To deploy customized Liberty applications to IBM Cloud Private, use a Helm chart. With a Helm chart, set metadata and rules for how the Liberty image is deployed in the Kubernetes cluster.
Requirements
Updates to this topic are available in GitHub. See the Liberty Helm chart Readme file, for the latest configuration information.
- /config
- The Liberty configuration directory.
- /logs
- The logs directory.
- /output
- The output directory.
ENV LOG_DIR /logs
ENV WLP_OUTPUT_DIR /opt/ibm/wlp/output
RUN mkdir /logs
&& ln -s $WLP_OUTPUT_DIR/defaultServer /output
&& ln -s /opt/ibm/wlp/usr/servers/defaultServer /config
![[18.0.0.1 and later]](../ng_v18001plus.gif)
Transaction service
<transaction recoverOnStartup="true" waitForRecovery="true" />
Accessing Liberty
From a browser, use http://external_ip:nodeport to access the application.
Configuration parameters
helm install --name liberty1 --namespace liberty-test1 liberty --debug
View the configuration parameters in the Liberty Helm chart Readme file. To deploy applications through the command line, see Deploying Liberty applications into IBM Cloud Private with a Liberty Helm chart.
After you configure the Helm chart, you can configure the Liberty server transaction log for availability. See Deploying applications in Liberty for more information about deploying the Liberty server.