Closed ldx closed 4 years ago
I think this is alright. I assume we'll have to manually specify the k8s version in the virtual-kubelet deployment manifest?
It's optional, by default the latest available kubectl version will be used (i.e. the latest tag will point to the image with the latest kubectl version).
Since init-cert uses kubectl, we need to ensure the right version is used (kubectl guarantees one minor version skew compatibility).
I added a script to build multiple images for each Kubernetes version between 1.12 and 1.18. Depending on the cluster, the use can simply change the image to e.g. elotl/init-cert:k8s-1.14 in a 1.14.x cluster.