From 6888a4956cb552bd7651199e14f2c718931d6361 Mon Sep 17 00:00:00 2001 From: Muhammed Karamuk Date: Tue, 12 Mar 2024 18:06:54 +0300 Subject: [PATCH] docs: Updated mysql secret generation command (#438) * docs: Updated mysql secret generation command By the change of mysql helm chart version the provided secret has at least three keys: - mysql-root-password - mysql-replication-password - mysql-password Otherwise mysql chart won't install. More information: https://artifacthub.io/packages/helm/bitnami/mysql#mysql-common-parameters * fix: Applied requested changes --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 862012c17..337d0cd7d 100644 --- a/README.md +++ b/README.md @@ -43,7 +43,7 @@ separately on-prem or leveraged as managed services. Assuming kubectl context points to the correct kubernetes cluster, first create kubernetes secrets that contain MySQL and Neo4j passwords. ```(shell) -kubectl create secret generic mysql-secrets --from-literal=mysql-root-password=datahub +kubectl create secret generic mysql-secrets --from-literal=mysql-root-password=datahub --from-literal=mysql-password=datahub kubectl create secret generic neo4j-secrets --from-literal=neo4j-password=datahub --from-literal=NEO4J_AUTH=neo4j/datahub ```