[kubeadm] Should we use stable identifier for kubernetes version

[krsna1729]

Instead of pinning the dot version kubernetesVersion: v1.12.0 is it better to use kubernetesVersion: stable-1.12 ?

[krsna1729]

@mcastelino

[fenrus75]

pinning is evil, it makes it hard to deploy urgent security fixes quickly. this is why clear Linux mostly bans or even undoes pinning

…

On Fri, Dec 7, 2018, 12:59 krsna1729 ***@***.*** wrote: @mcastelino <https://github.com/mcastelino> — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABPeFbl9vMELiP28BIyKckhqeOrNVM2Mks5u2tbOgaJpZM4ZJIqW> .

[mcastelino]

@fenrus75 @krsna1729 we should not need to pin. These files are included as part of the cloud-native-basic bundle. So they will/should rev whenever any kubernetes or CNI or CRI artifacts rev. So if the scripts break when we update cloud-native-bundle we need to fix the scripts. So when the user upgrades the scripts update. The user should never use files from this repo directly. They should always used the files that came with the bundle itself.

[mcastelino]

@krsna1729 with this change #14 we can close this right?

[krsna1729]

@mcastelino yes. I should have used the closes keyword.