You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With the recent migration of our Spark Operator repository from the GoogleCloudPlatform organization to the Kubeflow organization, it is essential to update our documentation to reflect the changes in the location of our Helm Charts. This update ensures users are directed to the correct repository for installations and updates.
The documentation currently directs users to add the Helm repository from the old location:
Required Change:
We need to update all occurrences of the Helm install links in the documentation to point to the new repository location under the Kubeflow organization:
The change needs to be reflected across multiple documentation pages wherever the Helm Chart installation instructions are mentioned. Review all documentation files for any references to the old repository, ensuring consistency and accuracy across the board.
Description:
With the recent migration of our Spark Operator repository from the GoogleCloudPlatform organization to the Kubeflow organization, it is essential to update our documentation to reflect the changes in the location of our Helm Charts. This update ensures users are directed to the correct repository for installations and updates.
The documentation currently directs users to add the Helm repository from the old location:
helm repo add spark-operator https://googlecloudplatform.github.io/spark-on-k8s-operator
Required Change:
We need to update all occurrences of the Helm install links in the documentation to point to the new repository location under the Kubeflow organization:
helm repo add spark-operator https://kubeflow.github.io/spark-operator
Scope of the Update:
The change needs to be reflected across multiple documentation pages wherever the Helm Chart installation instructions are mentioned. Review all documentation files for any references to the old repository, ensuring consistency and accuracy across the board.
Similar issues : #1926
The text was updated successfully, but these errors were encountered: