You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Craig Condit (Jira)" <ji...@apache.org> on 2021/09/28 17:27:00 UTC

[jira] [Created] (YUNIKORN-866) Support multiple versions of Kubernetes

Craig Condit created YUNIKORN-866:
-------------------------------------

             Summary: Support multiple versions of Kubernetes
                 Key: YUNIKORN-866
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-866
             Project: Apache YuniKorn
          Issue Type: Improvement
          Components: shim - kubernetes
            Reporter: Craig Condit


As we approach 1.0, we should think about how we will target multiple versions of kubernetes moving forward. Major vendors currently support versions as old as 1.18 and as new as 1.22. Additionally, for upgrades, we should ideally be building against the same version as the K8S cluster is running (+/- 1 version).

We also need to handle incompatibilities between old and new versions. For example, issues such as YUNIKORN-625 cannot currently be resolved while supporting such a wide version range, as APIs have transitioned from v1beta1 to v1 and dropped support for v1beta1 between 1.18 and 1.22.

To work around this, we could target the latest available internally, but modify build scripts to support building against older versions (possibly using different go.mod / go.sum files). For the case of things like v1beta vs. v1 of an API, we can use conditional compilation on the older versions to use the beta API instead of v1.




--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org