Features of Kubernetes:
Here are some of the Kubernetes features:
Capabilities of self-healingLoad Balancing and Horizontal ScalingLoose coupling of Infrastructure to each componentResource utilization has a high densityCentric-Application ManagementPredictable Infrastructure creationAutomated SchedulingAutomated rollback and rolloutsConsistent development in production and testingIt has Enterprise-ready featuresAuto-scalable Infrastructure
Advantages of Kubernetes:
Here, are some of the advantages of Kubernetes:
Kubernetes 1.17 Release:
The latest version of Kubernetes: 1.17 was released last month (December-2019). It consists of 22 enhancements, out of those, 14 are stable, 4 in alpha and 4 in beta. Kubernetes 1.17 version improves scalability in the cluster network. Also, it introduces the pod schedule, cluster storage, and runtime options for custom resource support.
New Features in Kubernetes 1.17:
In Kubernetes Certification 1.12, volume snapshots were introduced in alpha, but now Kubernetes version 1.17 promotes those volume snapshots to beta. This advanced feature can snapshot the cluster in a moment. Those snapshots can provide a new volume with old snapshots’ data. This helps to elaborate code-version and data-version operations.The default storage plug-ins are moved to CSI (Container Storage Interface), and it leads to independence on drivers for the core version. Earlier in Kubernetes 1.12, cloud provider labels were introduced only in beta. But, now it is available in both beta and alpha because of Kubernetes 1.17 version.
Volume Snapshots in Kubernetes:
Kubernetes also creates an abstraction layer between underlying systems and distributed application systems to agnostic the cluster specifics and application deployment. SIG, which is a Kubernetes storage, identifies critical functionality of snapshot operations for stateful workloads. Kubernetes users can handle use cases without API by providing trigger snapshot operations. At present, Kubernetes users empowered snapshot operations with clusters regardless of storage underlying. Also, Kubernetes snapshot acts as building blocks to develop storage administration and enterprise-grade features with backup solutions.
CSI Migration Beta:
Kubernetes provides volume plugin systems in which “in-tree” was code for the core Kubernetes. As we know, to add new volume, support was a tough challenge. Vendors wanted to support the storage system to Kubernetes, but it was not possible. Besides, the storage in the third-party code causes security issues and reliability issues in core binaries and the code were complicated to test. Later on, Container Storage Interface solves those issues. As there were many CSI drivers, the production became ready for the CSI model benefits. However, we didn’t force users to make the workload changes by breaking available API storage. The only possible way is to replace “in-tree plugin” with CSI. CSI(Container Storage Interface) migration enables in-tree storage plugin replacement with corresponding CSI drivers. Users cannot be able to identify the differences if CSI migration works properly. Users may depend on the in-tree storage functionality with the existing interface. If Kubernetes updates the cluster to enable the migration of CSI, then the stateful workloads and deployments continue to function behind the scenes of storage management operations. Kubernetes 1.17 version ensures storage APIs stability for the smooth upgrade promise. This involves backward capabilities. Existing feature behaviors, and API stability.
New features in Beta after Kubernetes 1.17:
Revamp of snapshot API volume.Added deletion secret to the snapshot content as an annotation.CSI snapshooter splits into two controllers external-snapshooter sidecar and common snapshot controller.Added a new finalizer to prevent the content API object of volume snapshot.
Volume Snapshots Requirements:
Volume Snapshot controller.Volume CRDs.CSI driver with volume snapshot beta.
Drivers supporting Volume Snapshots:
The volume snapshot feature depends on a common snapshot controller to the CRDs. Both the CRDs and snapshot controller are independent of CSI driver. There must be only one instance snapshot controller to install CRDs per cluster. Hence, Kubernetes distributors deploy the CRDs as the cluster management process. Kubernetes supports Flex, in-tree, and CSI volume plugins. But, whereas snapshot supports CSI drivers to use Kubernetes features on the cluster. The following CSI drivers support volume snapshots:
Portworx CSI DriverGCE Persistent DiskNetApp Trident
Conclusion:
We have discussed the features of the Kubernetes 1.17 release. These features enable user’s access with a single-line command to the latest upstream in 60 seconds. Snap store proxy controls the Kubernetes-worker charms, and CIS (Center for Internet Security) maintains the benchmark of Kubernetes 1.17. This is how Kubernetes 1.17 works.
Author Bio:
Anji Velagana, a graduate in Electronics and Communication Engineering from Jawaharlal Technological University, Kakinada. He is currently working as a Digital Marketing Analyst and Content Contributor for Mindmajix. He writes about various platforms like Data Science, Servicenow, Kubernetes, Business analysis, Performance testing, Mulesoft, Azure, SaltStack, and a few other courses. Contact him via anjivelagana@gmail.com and LinkedIn.
