You need to sign in or sign up before continuing.
Proposal: Test with near-line versions of Kubernetes
Summary
#1410 (closed) and surrounding issues provided great example to us on how our current targeting of major cloud service providers (~GKE ~EKS) is not sufficient. We should investigate at least cursory testing of near-line releases (maximum minor 1 version from latest upstream). If necessary, we should look to using k3s, RKE, or KinD.
- If using another cloud provider, we should attempt to make use of one that provides closer to the latest mainline, if not the latest mainline.
- If using a deployer tool, I would strongly suggest ephemeral environment scripting (if possible) to ensure updates, efficiency of resources, and cleanliness of the environments themselves.
Details
Currently, our 'CNG' CI cluster in GKE is 1.11.10-gke.5
Upstream Kubernetes is currently at 1.15.2
, with 1.16.0-alpha.3
coming long, and due in late September 2019.
platform | available |
---|---|
GKE | 1.12, 1.13 |
EKS | 1.11, 1.12, 1.13 |
DO-K | 1.13, 1.14, 1.15 |
deployer | available |
---|---|
RKE | 1.13.9,1.14.5,1.15.2 |
k3s | 1.14.5 |
KinD | 1.11.10,1.12.9,1.13.7,1.14.3,1.15.0 |
Edited by Jason Plum