Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when installing MLRun using Helm

See original GitHub issue

Hi, I tried to install MLRun by running the following commands:

helm --namespace mlrun install mlrun-kit --wait --set global.registry.url=<some custom Docker registry URL> --set global.registry.secretName=registry-credentials v3io-stable/mlrun-kit

But got this error:

Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: [ValidationError(CustomResourceDefinition.spec): unknown field "subresources" in io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.CustomResourceDefinitionSpec, ValidationError(CustomResourceDefinition.spec): unknown field "validation" in io.k8s.apiextensions-apiserver.pkg.apis.apiextensions.v1.CustomResourceDefinitionSpec]

I searched for this error and it seems that “subresources” and “validation” fields were removed in v1 CustomResourceDefinition.

So I dumped the template and validated it manually:

helm --namespace mlrun template mlrun-kit --wait --set global.registry.url=<some custom Docker registry URL> --set global.registry.secretName=registry-credentials v3io-stable/mlrun-kit > mlrun.yaml
kubectl apply --dry-run=client -f mlrun.yaml

But there were no errors! I also searched the template for a v1 CustomResourceDefinition instead of v1beta1 but there were none!

Can anyone help?

Kubernetes version: 1.20.4 Helm version: 3.5.2

Issue Analytics

State:
Created 3 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

Hedingbercommented, Feb 24, 2021

@AliMirlou Looking on their code - GitVersion is still there - indeed deprecated. Looking on the references to the getCapabilities function it’s being called only from the actions install uninstall and upgrade So yeah, as we said, when doing helm template this does not get evaluated

1reaction

Hedingbercommented, Feb 24, 2021

Hi @AliMirlou - thanks for reporting the issue. Just to explain what’s going on - this invalid CRD is coming from the mpi-operator helm chart which as you can see here is a requirement chart of the mlrun-kit helm chart As you can see here and here this chart “template” a different version for the crd based on your k8s version. I guess that when you helm template it doesn’t consider the server version, or just consider something else than in helm install and this is the reason you couldn’t find template with v1 That also explain why you could deploy it through kubectl apply without errors - in what you deployed the version was v1beta1 I have successfully reproduced your issue and working on a fix

Top Results From Across the Web

Install MLRun on Kubernetes

When the installation is complete, the helm command prints the URLs and Ports of all the MLRun CE services. Installing the Full Version#....

Source code for mlrun.config

__getattr__(part) except AttributeError: raise mlrun.errors.MLRunNotFoundError( "Attribute does not exist in config" ) # There is a bug in the installer ...

Installation and setup guide - MLRun

This guide outlines the steps for installing and running MLRun. MLRun has two main components, the service and the client (SDK):. MLRun service...

Installation Guide - MLRun

Open Jupyter Lab on jupyter-lab UI and run the code in examples/mlrun_basics.ipynb notebook. Note: You can change the ports by providing values to...

MLRun - Release UNKNOWN Iguazio

If it is not installed in your environment run !pip install ... Refer to the Helm installation instructions for more information.