[Umbrella] GCS FT API improvement

[kevin85421]

Search before asking

• I had searched in the issues and found no similar feature requirement.

Description

• [GCS FT] GCS FT misconfiguration #2694
• [GCS FT] Move GCS FT API from annotations to RayCluster CRD #2695
• [Feature] Update doc for GCS FT after API changes #2697

Use case

No response

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

[kevin85421]

/assign @rueian

[rueian]

👌

[kevin85421]

• Username (maybe v1.4.0 because Ray 2.41 doesn't release)
• Cleanup redis
• Validation

[rueian]

Hi @kevin85421 the two follow-ups are ready:
#2772
#2773

[rueian]

Follow ups:

• GCS FT redis username e2e test.
• [RayCluster][Feature] reject redis username to head pod out side of GcsFaultToleranceOptions #2796
• GCS FT document update to include an example of yaml.

[kevin85421]

Related PRs for v1.3.0:

• [RayCluster][Feature] add GcsFaultToleranceOptions to the RayCluster CRD [1/N] #2715
• [RayCluster][Feature] setup GCS FT annotations and the RAY_REDIS_ADDRESS env by the GcsFaultToleranceOptions #2721
• [Feature] Validation of RayFTEnabled is false and GcsFaultToleranceOption is not nil #2726
• [RayCluster] Validate RayClusterSpec for empty containers and GCS FT #2749
• [RayCluster][Feature] add redis password to head pod from GcsFaultToleranceOptions  #2731
• [RayCluster] Validate GCSFaultToleranceOptions and redis password #2754
• [GCS FT] Unify configuring Gcs FT into a single function #2755
• [GCS FT] Add e2e tests for configuring GCS FT with annotations #2766
• [GCS FT] More validations for configuring GCS FT with envs and annotations #2772
• [GCS FT] Redis e2e cleanup check #2773
• [RayCluster][Feature] add redis username to head pod from GcsFaultToleranceOptions #2760
• [RayCluster][Feature] reject redis username to head pod out side of GcsFaultToleranceOptions #2796