4 ms·
I've done a number of 1.5 to 1.9 migrations, if you need help figuring out what API endpoints/etc have changed I can give you some guidance if you ping me on k8
by swozey 9y ago
I've done a number of 1.5 to 1.9 migrations, if you need help figuring out what API endpoints/etc have changed I can give you some guidance if you ping me on k8s slack; mikej.
Once you get onto 1.8+ w/ CRDs you can manage your SSL certs automatically via Jetstacks Certmanager; https://github.com/jetstack/cert-manager/tree/master/contrib/charts/cert-manager/templates https://github.com/jetstack/cert-manager/tree/master/contrib...
- yebyen 9y agoThanks! I will check it out! It just hasn't been a priority. I have no need for RBAC at this point, as I am the only cluster admin, and the whole network is fairly well isolated. I couldn't really think of a good reason to not upgrade when it came time to kubeadm init again, but then I realized I could probably save ten minutes by not upgrading, it was down, and I didn't know what the immediate consequences of adding RBAC would be for my existing Jenkins deployment and jobs. Chances are it would have worked.
- swozey 9y agoHonestly for the situation you presented you'll find very few QOL improvements by upgrading. You could probably sit on 1.5 forever on that system (internal jenkins) forever.
- yebyen 9y agoThe biggest driver is actually just to not be behind. You can tell already from what little conversation we've had that "always be upgrading" is not a cultural practice here (yet.) We have regular meetings about changing that! Had two just yesterday. Chuckle