From 4cee1b5cedea02e8a4affa934557d6f5a0e7035f Mon Sep 17 00:00:00 2001 From: Carlos Rodriguez Hernandez Date: Wed, 31 Oct 2018 11:46:44 +0100 Subject: [PATCH] Update Node with OSBA Mongodb instructions --- bitnami/node/Chart.yaml | 2 +- bitnami/node/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/bitnami/node/Chart.yaml b/bitnami/node/Chart.yaml index aec310c93a..38a83068a9 100644 --- a/bitnami/node/Chart.yaml +++ b/bitnami/node/Chart.yaml @@ -1,5 +1,5 @@ name: node -version: 6.2.2 +version: 6.2.3 appVersion: 8.12.0 description: Event-driven I/O server-side JavaScript environment based on V8 keywords: diff --git a/bitnami/node/README.md b/bitnami/node/README.md index e243eb871a..cca472bae6 100644 --- a/bitnami/node/README.md +++ b/bitnami/node/README.md @@ -211,7 +211,7 @@ ingress: 4. Deploy the helm chart: ``` - $ helm install --name node-app --set mongodb.install=false,externaldb.broker.serviceInstanceName=azure-mongodb-instance bitnami/node + $ helm install --name node-app --set mongodb.install=false,externaldb.broker.serviceInstanceName=azure-mongodb-instance,externaldb.ssl=true bitnami/node ``` Once the instance has been provisioned in Azure, a new secret should have been automatically created with the connection parameters for your application.