Bitnami/charts
2
0
Fork 0
mirror of https://github.com/bitnami/charts.git synced 2026-03-16 14:57:08 +08:00
Code Issues Packages Projects Releases Wiki Activity

[bitnami/several] Bump version and update READMEs (#7069)

Browse Source 
* [bitnami/several] Bump version and update READMEs

* Replace TM with ™

* Replace R with ®

* Fix version
This commit is contained in:
Carlos Rodríguez Hernández
2021-07-27 17:41:53 +02:00
committed by GitHub
parent 4c867335c5
commit 6340bff66f
71 changed files with 1005 additions and 1002 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
bitnami/mongodb/templates/NOTES.txt
View File

@@ -32,12 +32,12 @@ In order to replicate the container startup scripts execute this command:
{{- if and (eq .Values.architecture "replicaset") .Values.externalAccess.enabled (not .Values.externalAccess.autoDiscovery.enabled) (not (eq $replicaCount $loadBalancerIPListLength )) (eq .Values.externalAccess.service.type "LoadBalancer") }}
###############################################################################
### ERROR: You enabled external access to MongoDB(R) nodes without specifying ###
### the array of load balancer IPs for MongoDB(R) nodes. ###
### ERROR: You enabled external access to MongoDB® nodes without specifying ###
### the array of load balancer IPs for MongoDB® nodes. ###
###############################################################################
This deployment will be incomplete until you configure the array of load balancer
IPs for MongoDB(R) nodes. To complete your deployment follow the steps below:
IPs for MongoDB® nodes. To complete your deployment follow the steps below:
1. Wait for the load balancer IPs (it may take a few minutes for them to be available):
@@ -66,7 +66,7 @@ IPs for MongoDB(R) nodes. To complete your deployment follow the steps below:
WARNING
By not enabling "mongodb.auth.enabled" you have most likely exposed the
MongoDB(R) service externally without any authentication mechanism.
MongoDB® service externally without any authentication mechanism.
For security reasons, we strongly suggest that you enable authentiation
setting the "mongodb.auth.enabled" parameter to "true".
@@ -76,7 +76,7 @@ IPs for MongoDB(R) nodes. To complete your deployment follow the steps below:
** Please be patient while the chart is being deployed **
MongoDB(R) can be accessed on the following DNS name(s) and ports from within your cluster:
MongoDB® can be accessed on the following DNS name(s) and ports from within your cluster:
{{- if eq .Values.architecture "replicaset" }}
{{ join "\n" $mongoList | nindent 4 }}
@@ -101,7 +101,7 @@ To get the password for "{{ .Values.auth.username }}" run:
{{- end }}
To connect to your database, create a MongoDB(R) client container:
To connect to your database, create a MongoDB® client container:
kubectl run --namespace {{ template "mongodb.namespace" . }} {{ template "mongodb.fullname" . }}-client --rm --tty -i --restart='Never' --env="MONGODB_ROOT_PASSWORD=$MONGODB_ROOT_PASSWORD" --image {{ template "mongodb.image" . }} --command -- bash
@@ -120,17 +120,17 @@ To connect to your database nodes from outside, you need to add both primary and
{{- if eq "NodePort" .Values.externalAccess.service.type }}
{{- if .Values.externalAccess.service.domain }}
MongoDB(R) nodes domain: Use your provided hostname to reach MongoDB(R) nodes, {{ .Values.externalAccess.service.domain }}
MongoDB® nodes domain: Use your provided hostname to reach MongoDB® nodes, {{ .Values.externalAccess.service.domain }}
{{- else }}
MongoDB(R) nodes domain: you can reach MongoDB(R) nodes on any of the K8s nodes external IPs.
MongoDB® nodes domain: you can reach MongoDB® nodes on any of the K8s nodes external IPs.
kubectl get nodes -o wide
{{- end }}
MongoDB(R) nodes port: You will have a different node port for each MongoDB(R) node. You can get the list of configured node ports using the command below:
MongoDB® nodes port: You will have a different node port for each MongoDB® node. You can get the list of configured node ports using the command below:
echo "$(kubectl get svc --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ template "mongodb.name" . }},app.kubernetes.io/instance={{ .Release.Name }},app.kubernetes.io/component=mongodb,pod" -o jsonpath='{.items[*].spec.ports[0].nodePort}' | tr ' ' '\n')"
@@ -139,11 +139,11 @@ To connect to your database nodes from outside, you need to add both primary and
NOTE: It may take a few minutes for the LoadBalancer IPs to be available.
Watch the status with: 'kubectl get svc --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ template "mongodb.name" . }},app.kubernetes.io/instance={{ .Release.Name }},app.kubernetes.io/component=mongodb,pod" -w'
MongoDB(R) nodes domain: You will have a different external IP for each MongoDB(R) node. You can get the list of external IPs using the command below:
MongoDB® nodes domain: You will have a different external IP for each MongoDB® node. You can get the list of external IPs using the command below:
echo "$(kubectl get svc --namespace {{ .Release.Namespace }} -l "app.kubernetes.io/name={{ template "mongodb.name" . }},app.kubernetes.io/instance={{ .Release.Name }},app.kubernetes.io/component=mongodb,pod" -o jsonpath='{.items[*].status.loadBalancer.ingress[0].ip}' | tr ' ' '\n')"
MongoDB(R) nodes port: {{ .Values.externalAccess.service.port }}
MongoDB® nodes port: {{ .Values.externalAccess.service.port }}
{{- end }}
@@ -176,7 +176,7 @@ To connect to your database from outside the cluster execute the following comma
{{- if .Values.metrics.enabled }}
To access the MongoDB(R) Prometheus metrics, get the MongoDB(R) Prometheus URL by running:
To access the MongoDB® Prometheus metrics, get the MongoDB® Prometheus URL by running:
kubectl port-forward --namespace {{ .Release.Namespace }} svc/{{ include "mongodb.fullname" . }}-metrics {{ .Values.metrics.service.port }}:{{ .Values.metrics.service.port }} &
echo "Prometheus Metrics URL: http://127.0.0.1:{{ .Values.metrics.service.port }}/metrics"