[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/etcd/values.yaml

@@ -78,7 +78,7 @@ image:
   ## @param image.pullPolicy etcd image pull policy
   ## 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
   ## @param image.pullSecrets [array] etcd image pull secrets
@@ -321,7 +321,7 @@ containerSecurityContext:
   seccompProfile:
     type: "RuntimeDefault"
 ## etcd 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
@@ -465,7 +465,7 @@ nodeAffinityPreset:
 ##
 affinity: {}
 ## @param nodeSelector [object] 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 [array] Tolerations for pod assignment
@@ -553,7 +553,7 @@ service:
   ##
   metricsPortNameOverride: ""
   ## @param service.loadBalancerIP loadBalancerIP for the etcd service (optional, cloud specific)
-  ## ref: https://kubernetes.io/docs/user-guide/services/#type-loadbalancer
+  ## ref: https://kubernetes.io/docs/concepts/services-networking/service/#type-loadbalancer
   ##
   loadBalancerIP: ""
   ## @param service.loadBalancerSourceRanges [array] Load Balancer source ranges
@@ -599,7 +599,7 @@ service:
 ##
 
 ## Enable persistence using Persistent Volume Claims
-## ref: https://kubernetes.io/docs/user-guide/persistent-volumes/
+## ref: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
 ##
 persistence:
   ## @param persistence.enabled If true, use a Persistent Volume Claim. If false, use emptyDir.
@@ -665,7 +665,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
@@ -856,7 +856,7 @@ disasterRecovery:
     ##
     podAnnotations: {}
     ## Configure resource requests and limits for snapshotter containers
-    ## 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
@@ -874,7 +874,7 @@ disasterRecovery:
       requests: {}
 
     ## @param disasterRecovery.cronjob.nodeSelector Node labels for cronjob pods assignment
-    ## Ref: https://kubernetes.io/docs/user-guide/node-selection/
+    ## Ref: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/
     ##
     nodeSelector: {}
     ## @param disasterRecovery.cronjob.tolerations Tolerations for cronjob pods assignment