[bitnami/*] Fix ref links (in comments) (#21822)

* docs(kubernetes): replace broken links to ./user-guide/

with current links to ./concepts/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken links to ./user-guide/persistent-volumes

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken links to ./user-guide/compute-resources/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken links to ./user-guide/node-selection/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken ref links to ./user-guide/services/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken ref links to ./user-guide/ingress/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken ref links for pullPolicy

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken ref links to compute-resources

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): replace broken ref links to master branch

of kubernetes/ingress-nginx/

Signed-off-by: Bryan Dady <bryan@dady.us>

* docs(kubernetes): fixup remaining "user-guide" ref links

Signed-off-by: Bryan Dady <bryan@dady.us>

* fix(harbor): revert accidental additions

Revert unintended changes resulting from rebase

Signed-off-by: Bryan Dady <bryan@dady.us>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* bitnami/grafana-operator fix docs(README)
revert accidental (rebase) edit to operator.namespaceScope description

Signed-off-by: Bryan Dady <bryan@dady.us>

* Update README.md with readme-generator-for-helm

Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>

* Remove duplicate comments in grafana values

Signed-off-by: Jose Antonio Carmona <jcarmona@vmware.com>

---------

Signed-off-by: Bryan Dady <bryan@dady.us>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Jose Antonio Carmona <jcarmona@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>
This commit is contained in:
Bryan Dady
2024-01-11 06:40:00 -07:00
committed by GitHub
parent 7e4508707d
commit e4fa296106
114 changed files with 1287 additions and 1289 deletions

View File

@@ -42,7 +42,7 @@ image:
debug: false
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets.
@@ -724,7 +724,7 @@ nodeAffinityPreset:
##
affinity: {}
## @param nodeSelector Node labels for pod assignment. Evaluated as a template
## ref: https://kubernetes.io/docs/user-guide/node-selection/
## ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
##
nodeSelector: {}
## @param tolerations Tolerations for pod assignment. Evaluated as a template
@@ -769,7 +769,7 @@ containerSecurityContext:
type: "RuntimeDefault"
## RabbitMQ containers' resource requests and limits
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## We usually recommend not to specify default resources and to leave this as a conscious
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube. If you do want to specify resources, uncomment the following
@@ -1126,7 +1126,7 @@ service:
## Configure the ingress resource that allows you to access the
## RabbitMQ installation. Set up the URL
## ref: https://kubernetes.io/docs/user-guide/ingress/
## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/
##
ingress:
## @param ingress.enabled Enable ingress resource for Management console
@@ -1145,7 +1145,7 @@ ingress:
hostname: rabbitmq.local
## @param ingress.annotations Additional annotations for the Ingress resource. To enable certificate autogeneration, place here your cert-manager annotations.
## For a full list of possible ingress annotations, please see
## ref: https://github.com/kubernetes/ingress-nginx/blob/master/docs/user-guide/nginx-configuration/annotations.md
## ref: https://github.com/kubernetes/ingress-nginx/blob/main/docs/user-guide/nginx-configuration/annotations.md
## Use this parameter to set the required annotations for cert-manager, see
## ref: https://cert-manager.io/docs/usage/ingress/#supported-annotations
##
@@ -1432,7 +1432,7 @@ volumePermissions:
digest: ""
## Specify a imagePullPolicy
## Defaults to 'Always' if image tag is 'latest', else set to 'IfNotPresent'
## ref: https://kubernetes.io/docs/user-guide/images/#pre-pulling-images
## ref: https://kubernetes.io/docs/concepts/containers/images/#pre-pulled-images
##
pullPolicy: IfNotPresent
## Optionally specify an array of imagePullSecrets (secrets must be manually created in the namespace)
@@ -1443,7 +1443,7 @@ volumePermissions:
##
pullSecrets: []
## Init Container resource requests and limits
## ref: https://kubernetes.io/docs/user-guide/compute-resources/
## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
## We usually recommend not to specify default resources and to leave this as a conscious
## choice for the user. This also increases chances charts run on environments with little
## resources, such as Minikube. If you do want to specify resources, uncomment the following