-
Notifications
You must be signed in to change notification settings - Fork 46
Description
Hello,
Thank you for the work you’re doing with this project! I’m reaching out regarding the dependency on k8s.io/kubernetes. Currently, the project relies on several internal packages from k8s.io/kubernetes, such as:
k8s.io/kubernetes/pkg/scheduler/apis/config/schemek8s.io/kubernetes/pkg/scheduler/apis/configk8s.io/kubernetes/pkg/kubelet/pluginmanager/cachek8s.io/kubernetes/pkg/util/filesystemk8s.io/kubernetes/pkg/kubelet/apis/config
However, according to the official Go documentation for Kubernetes, using k8s.io/kubernetes as a library is no longer supported. The documentation suggests using Kubernetes' published components instead, as k8s.io/kubernetes is intended only for building and running Kubernetes itself, not for use as a dependency in other projects.

Additionally, in Kubernetes version 1.26 and above, direct imports from k8s.io/kubernetes are no longer supported in the same way. Internal packages have been refactored, and dependencies on k8s.io/kubernetes can lead to version conflicts and compatibility issues, especially with projects that need to stay up-to-date with the latest Kubernetes versions.
Do you currently have any plans to replace the k8s.io/kubernetes dependency with staging modules (like k8s.io/client-go, k8s.io/apimachinery, k8s.io/api, k8s.io/utils), or is there an alternative approach under consideration?
Thank you for considering this request, and I look forward to any updates on this matter!