Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm chart references non-existent version v1beta2-1.4.2-3.5.0 #2034

Closed
tasgon opened this issue May 20, 2024 · 3 comments · Fixed by #2044
Closed

Helm chart references non-existent version v1beta2-1.4.2-3.5.0 #2034

tasgon opened this issue May 20, 2024 · 3 comments · Fixed by #2044

Comments

@tasgon
Copy link

tasgon commented May 20, 2024

Description

#1998 set the Helm chart's default appVersion to v1beta2-1.4.2-3.5.0, which fails to pull and does not appear to be listed on https://hub.docker.com/r/kubeflow/spark-operator/tags.

Reproduction Code [Required]

helm repo add spark-operator https://kubeflow.github.io/spark-operator
helm install spark spark-operator/spark-operator --namespace spark-operator --create-namespace

Steps to reproduce the behavior:

Install the spark operator through Helm as described in the README.

Expected behavior

The spark-operator pod starts successfully.

Actual behavior

Failed to pull image "docker.io/kubeflow/spark-operator:v1beta2-1.4.2-3.5.0": rpc error: code = NotFound desc = failed to pull and unpack image "docker.io/kubeflow/spark-operator:v1beta2-1.4.2-3.5.0": failed to resolve reference "docker.io/kubeflow/spark-operator:v1beta2-1.4.2-3.5.0": docker.io/kubeflow/spark-operator:v1beta2-1.4.2-3.5.0: not found
@alstjs37
Copy link

Did you solved it ?
I have same problem too,,

@tasgon
Copy link
Author

tasgon commented May 24, 2024

You can clone the repo locally and modify Chart.yaml to use the correct appVersion or you can override image.tag using either --set image.tag=<correct_tag> or a custom values.yml file.

@alstjs37
Copy link

Thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants