[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>

bitnami/ghost/values.yaml

@@ -77,7 +77,7 @@ image:
   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.
@@ -274,7 +274,7 @@ nodeAffinityPreset:
 ##
 affinity: {}
 ## @param nodeSelector Node labels for pod assignment
-## 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
@@ -282,7 +282,7 @@ nodeSelector: {}
 ##
 tolerations: []
 ## Ghost 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/
 ## @param resources.limits The resources limits for the Ghost container
 ## @param resources.requests The requested resources for the Ghost container
 ##
@@ -435,7 +435,7 @@ service:
   ##     timeoutSeconds: 300
   sessionAffinityConfig: {}
 ## Configure the ingress resource that allows you to access the Ghost installation
-## ref: https://kubernetes.io/docs/user-guide/ingress/
+## ref: https://kubernetes.io/docs/concepts/services-networking/ingress/
 ##
 ingress:
   ## @param ingress.enabled Enable ingress record generation for Ghost
@@ -456,7 +456,7 @@ ingress:
   path: /
   ## @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
   ##
@@ -548,7 +548,7 @@ ingress:
 ## @section Persistence Parameters
 
 ## Persistence Parameters
-## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
+## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
 ##
 persistence:
   ## @param persistence.enabled Enable persistence using Persistent Volume Claims
@@ -608,7 +608,7 @@ volumePermissions:
     ##
     pullSecrets: []
   ## Init container's resource requests and limits
-  ## ref: https://kubernetes.io/docs/user-guide/compute-resources/
+  ## ref: https://kubernetes.io/docs/concepts/configuration/manage-compute-resources-container/
   ## @param volumePermissions.resources.limits The resources limits for the init container
   ## @param volumePermissions.resources.requests The requested resources for the init container
   ##
@@ -657,7 +657,7 @@ mysql:
   ##
   primary:
     ## MySQL Primary Persistence parameters
-    ## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
+    ## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
     ## @param mysql.primary.persistence.enabled Enable persistence on MySQL using PVC(s)
     ## @param mysql.primary.persistence.storageClass Persistent Volume storage class
     ## @param mysql.primary.persistence.accessModes [array] Persistent Volume access modes