Kubernetes 1.15 released!
In the midst of #HPEDiscover we witnessed the release of Kubernetes 1.15. As usual, there’s a ton of features and improvements. I’ve cherry picked a few things worthy of mention from the release announcement.
I listened to a lightning talk a few KubeCons back where a fairly radical idea was vented. Once all the extensibility (meaning out-of-tree extensions) are done, why not make core components extensions? Rip everything out and put it back in as extensions? In the same talk it was also brushed that CSI is more or less the guinea pig for this concept as CSI is a complete rewrite of the storage subsystem and there’s ambitions to port in-tree drivers to out-of-tree CSI drivers, hence not maintained in kubernetes/kubernetes. Kubernetes 1.15 contains more new APIs to manage CRDs (Custom Resource Definitions) and further improve the extensibility.
Among the quality of life improvements for cluster lifecycle is that kubeadm moved HA bootstrapping to beta. This means that kubeadm draws a whole lot closer to produce production ready Kubernetes clusters OOB. Still some work to do as the documentation is a tad too thick still.
Most importantly, kubeadm got a new logo which can be found on the CNCF installer landscape.
Volume cloning is now introduced as an alpha feature. It must be enabled manually with the --feature-gates=VolumePVCDataSource=true feature gate. This will ultimately give users a portable way to create clones from PVCs. Many vendors, such as ourselves, allow cloning through annotating the PVC. As such:
--- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: my-pvc-clone annotations: hpe.com/cloneOfPVC: my-source-pvc spec: storageClassName: my-storageclass accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
This is what the same operation would look like with a CSI driver that implements CLONE_VOLUME:
--- apiVersion: v1 kind: PersistentVolumeClaim metadata: name: my-pvc-clone spec: storageClassName: my-storageclass dataSource: name: my-source-pvc kind: PersistentVolumeClaim accessModes: - ReadWriteOnce resources: requests: storage: 1Gi
As you can see, all the vendor ramblings have been removed. Cloning is implemented in the CSI hostpath plugin if you want to play around with it.
There will be a webinar on the 23rd of July where the release team discusses the new features. Also, don’t forget KubeCon in San Diego November 18-21.
