kubermatic / kubermatic/flowmatic
Addon is not compatible with kubernetes 1.22.X
- Dominant language
- Shell
- Stars
- 1
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
We tried installing the addon on a user cluster with K8s version 1.22.15, and the installation didn't go through. The `KfDef` CRD definition has api version [apiextensions.k8s.io/v1beta1](https://github.com/kubermatic/flowmatic/blob/master/addon/kubeflow/kubeflow-controller.yaml#L23) which is deprecated, same is true for nvdia [ClusterPolicy](https://github.com/kubermatic/flowmatic/blob/master/addon/kubeflow/nvidia-gpu-operator.yaml#L18) CRD.
I updated the CRD to newer API version but then we encountered similar problems with the apps which are deployed by operator based on kubeflow definition(kfdef) as they also have objects which deprecated API versions.
Contributor guide
Research direction
Start with addon/kubeflow/kubeflow-controller.yaml and addon/kubeflow/nvidia-gpu-operator.yaml, focusing on the deprecated CRD API versions identified in the issue. Then inspect the applications deployed from the Kubeflow definition for other deprecated APIs. Done means the addon installs successfully on Kubernetes 1.22.15 without deprecated API incompatibilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100