404 Not Found https://googlecloudplatform.github.io/spark-on-k8s-operator/index.yaml

Question

404 Not Found https://googlecloudplatform.github.io/spark-on-k8s-operator/index.yaml

Closed this issue 6 months ago · 13 comments

Can't pull the spark-on-k8s-operator Helm chart as of 6 hours ago with the latest environment deployment. Seems to have been triggered by @zijianjoy. Did the deployment not run from the correct branch or something?

404: https://googlecloudplatform.github.io/spark-on-k8s-operator/index.yaml

ksemele commented 6 months ago

same...

Answer 1 · 2024-03-14T02:43:31.000Z

Getting same error

# [2024-03-13T18:58:30.175Z] Error:: looks like "https://googlecloudplatform.github.io/spark-on-k8s-operator" 
# is not a valid chart repository or cannot be reached: failed to fetch https://googlecloudplatform.github.io/spark-on-k8s-operator/index.yaml : 404 Not Found

Answer 2 · 2024-03-14T07:55:27.000Z

I am also getting same error since few hours ago

Answer 3 · 2024-03-14T08:21:20.000Z

Look like in this deployment it deployed into https://kubeflow.github.io/spark-operator/ instead https://googlecloudplatform.github.io/spark-on-k8s-operator/

Answer 4 · 2024-03-14T08:31:28.000Z

@kimisu1 You're right, looks like the yaml is there. Confirmed using https://kubeflow.github.io/spark-operator/ instead works. Cheers!

Answer 5 · 2024-03-14T08:37:59.000Z

https://charts.helm.sh/incubator/ works too... but what is correct repo address now?

Answer 6 · 2024-03-14T08:41:59.000Z

@ksemele Probably this one https://kubeflow.github.io/spark-operator/ because spark-operator not in GoogleCloudPlatform currently it in kubeflow

Answer 7 · 2024-03-14T10:08:19.000Z

Changing to the following helm dependency worked for me this morning. Version omitted as I'm on an old version.

dependencies:
- name: spark-operator
  repository: https://kubeflow.github.io/spark-operator
  version: ?.?.?
  condition: spark-operator.enabled

Would be good to know if this is correct moving forward as others have said.

Answer 8 · 2024-03-14T12:22:25.000Z

Look like in this deployment it deployed into https://kubeflow.github.io/spark-operator/ instead https://googlecloudplatform.github.io/spark-on-k8s-operator/

This worked for us too, thanks!!

Answer 9 · 2024-03-14T12:25:54.000Z

same here: this one worked for me :
`resource "helm_release" "main" {
depends_on = [ var.module_depends_on, kubernetes_namespace.main, kubernetes_namespace.spark_apps ]

chart           = "spark-operator"

repository      = "https://kubeflow.github.io/spark-operator"
version         = "1.1.27"


name      		= "spark-operator"`

Answer 10 · 2024-03-14T17:28:22.000Z

Thanks for reporting the issue. Yes, this issue is due to the repo migration to Kubeflow org. We will create a PR to update the Helm chart and verify the Github workflows.
FYI... @yuchaoran2011

Answer 11 · 2024-03-14T20:40:42.000Z

Hello everyone,

yes I triggered the repo migration from googlecloudplatform to kubeflow, thus causing https://kubeflow.github.io/spark-operator/index.yaml being the new endpoint. You can find more detail about this move in #1928.

Thanks for taking the effort to migrate the rest of related artifacts. cc @andreyvelich to coordinate those changes.

Answer 12 · 2024-03-15T14:47:40.000Z

Thanks for the guidance! I'll close this ticket, but please consider pinning this issue afterwards so that other people can more easily find the resolution to this issue.

There was no mention of this change in this repo. Additionally, I personally had no idea kubeflow/community even existed (no mention in README or anything), let alone to look there for issues like this.