Run make helm-docs

Signed-off-by: Yi Chen <[email protected]>

Author: ChenYi015

helm-chart/kuberay-operator/README.md

@@ -167,18 +167,14 @@ spec:
 | featureGates[1].enabled | bool | `false` |  |
 | metrics.enabled | bool | `true` | Whether KubeRay operator should emit control plane metrics. |
 | operatorCommand | string | `"/manager"` | Path to the operator binary |
+| useKubernetesProxy | bool | `false` |  |
 | leaderElectionEnabled | bool | `true` | If leaderElectionEnabled is set to true, the KubeRay operator will use leader election for high availability. |
 | rbacEnable | bool | `true` | If rbacEnable is set to false, no RBAC resources will be created, including the Role for leader election, the Role for Pods and Services, and so on. |
 | crNamespacedRbacEnable | bool | `true` | When crNamespacedRbacEnable is set to true, the KubeRay operator will create a Role for RayCluster preparation (e.g., Pods, Services) and a corresponding RoleBinding for each namespace listed in the "watchNamespace" parameter. Please note that even if crNamespacedRbacEnable is set to false, the Role and RoleBinding for leader election will still be created.  Note: (1) This variable is only effective when rbacEnable and singleNamespaceInstall are both set to true. (2) In most cases, it should be set to true, unless you are using a Kubernetes cluster managed by GitOps tools such as ArgoCD. |
 | singleNamespaceInstall | bool | `false` | When singleNamespaceInstall is true: - Install namespaced RBAC resources such as Role and RoleBinding instead of cluster-scoped ones like ClusterRole and ClusterRoleBinding so that   the chart can be installed by users with permissions restricted to a single namespace.   (Please note that this excludes the CRDs, which can only be installed at the cluster scope.) - If "watchNamespace" is not set, the KubeRay operator will, by default, only listen   to resource events within its own namespace. |
+| watchNamespace | list | `[]` | The KubeRay operator will watch the custom resources in the namespaces listed in the "watchNamespace" parameter. |
 | env | string | `nil` | Environment variables. |
 | resources | object | `{"limits":{"cpu":"100m","memory":"512Mi"}}` | Resource requests and limits for containers. |
-| livenessProbe.initialDelaySeconds | int | `10` |  |
-| livenessProbe.periodSeconds | int | `5` |  |
-| livenessProbe.failureThreshold | int | `5` |  |
-| readinessProbe.initialDelaySeconds | int | `10` |  |
-| readinessProbe.periodSeconds | int | `5` |  |
-| readinessProbe.failureThreshold | int | `5` |  |
 | podSecurityContext | object | `{}` | Set up `securityContext` to improve Pod security. |
 | service.type | string | `"ClusterIP"` | Service type. |
 | service.port | int | `8080` | Service port. |

helm-chart/kuberay-operator/values.yaml

@@ -172,13 +172,13 @@ resources:
   #   cpu: 100m
   #   memory: 512Mi
 
-# @Ignore -- Pod liveness probe configuration.
+# @ignore -- Pod liveness probe configuration.
 livenessProbe:
   initialDelaySeconds: 10
   periodSeconds: 5
   failureThreshold: 5
 
-# @Ignore -- Pod readiness probe configuration.
+# @ignore -- Pod readiness probe configuration.
 readinessProbe:
   initialDelaySeconds: 10
   periodSeconds: 5